gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2019-12-11	Add additional packages to go branch	Michael Pratt
	We're missing several packages that runsc doesn't depend on. Most notable are several tcpip link packages. To find packages, I looked at a diff of directories on master vs go: $ bazel build //:gopath $ find bazel-bin/gopath/src/gvisor.dev/gvisor/ -type d > /tmp/gopath.txt $ find . -type d > /tmp/master.txt $ sed 's\|bazel-bin/gopath/src/gvisor.dev/gvisor/\|\|' < /tmp/gopath.txt > /tmp/gopath.trunc.txt $ sed 's\|./\|\|' < /tmp/master.txt > /tmp/master.trunc.txt $ vimdiff /tmp/gopath.trunc.txt /tmp/master.trunc.txt Testing packages are still left out because :gopath can't depend on testonly targets... PiperOrigin-RevId: 285049029
2019-10-08	Add additional dependencies to :gopath tree.	Nicolas Lacasse
	PiperOrigin-RevId: 273586605
2019-07-09	build: add nogo for static validation	Adin Scannell
	PiperOrigin-RevId: 257297820
2019-06-01	Add tooling for Go-compatible branch.	Adin Scannell
	The WORKSPACE go_repositories can be generated from a standard go.mod file. Add the necessary gazelle hooks to do so, and include a test that sanity checks there are no changes. This go.mod file will be used in a subsequent commit to generate a go gettable branch of the repository. This commit also adds a tools/go_branch.sh script, which given an existing go branch in the repository, will add an additional synthetic change to the branch bringing it up-to-date with HEAD. As a final step, a cloudbuild script is included, which can be used to automate the process for every change pushed to the repository. This may be used after an initial go branch is pushed, but this is manual process. PiperOrigin-RevId: 251095016
2019-04-04	BUILD: Add useful go_path target	Adin Scannell
	Change-Id: Ibd6d8a1a63826af6e62a0f0669f8f0866c8091b4 PiperOrigin-RevId: 242037969
2018-04-28	Check in gVisor.	Googler
	PiperOrigin-RevId: 194583126 Change-Id: Ica1d8821a90f74e7e745962d71801c598c652463