gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-12-29	Exclude changing generated file from go_branch.	Adin Scannell
	PiperOrigin-RevId: 349491589
2020-12-09	Refactor the Makefile to avoid recursive Make.	Adin Scannell
	Recursive make is difficult to follow and debug. Drop this by using internal functions, which, while difficult, are easier than trying to following recursive invokations. Further simplify the Makefile by collapsing the image bits and removing the tools/vm directory, which is effectively unused. Fixes #4952 PiperOrigin-RevId: 346569133
2020-11-23	Don't rely on HOME for tools/go_branch.sh	Adin Scannell
	PiperOrigin-RevId: 343885770
2020-10-30	Add the gVisor admission webhook	Kevin Krakauer
	PiperOrigin-RevId: 339913577
2020-10-29	[infra] Deflake Go / generate (pull_request.	Ayush Ranjan
	#4673 does not seem to work. Try this new approach. PiperOrigin-RevId: 339754794
2020-10-28	[infra] Deflake Go / generate (pull_request) GitHub action.	Ayush Ranjan
	As you can see https://github.com/google/gvisor/commits/master, there are a lot of red commits. This is because the Go / generate GitHub action flakes. On merge, two variants of this workflow run: - one triggered by the pull request (copybara force pushes to the PR right before merge) - one triggered by the push (merge) If the push action ends up finishing before the pull request action can run go_branch.sh, then the changes that go_branch.sh makes is already pushed to the remote go branch. Consequently, the pull request action ends up having nothing to commit causing this action to fail. This change also fixes lint warnings. Now we skip running the go_branch.sh if we find that our current working commit has already been committed to remote. PiperOrigin-RevId: 339586760
2020-08-03	Include shim binaries in the Go branch.	Adin Scannell
	PiperOrigin-RevId: 324615016
2020-05-20	Normalize permissions in the go branch.	Adin Scannell
	Fixes #2722
2020-05-18	Implement Go branch updater with GitHub actions.	Adin Scannell
	PiperOrigin-RevId: 312155686
2019-11-25	Fix typo in go_branch.sh script.	Adin Scannell
	With the ticks, the command `master` is actually be run and the output included (which is nothing). This is confusing, as we actually mean to say "master" in the description of the Go branch. PiperOrigin-RevId: 282426081
2019-10-31	Add LICENSE and AUTHORS to the go branch.	Adin Scannell
	Also, construct the README directly so that edits can be made. PiperOrigin-RevId: 277782095
2019-09-10	Fix minor Kokoro issues.	Adin Scannell
	A recent Kokoro change pointed to go_tests.cfg (in line with the other configurations), which unfortunately broke the presubmits. This change also enabled the KVM tests, which were still using a remote execution strategy. This fixes both of these issues and allows presubmits to pass. One additional test was caught with this case, which seems to have been broken. It's unclear why this was not being caught. PiperOrigin-RevId: 268166291
2019-06-13	Update canonical repository.	Adin Scannell
	This can be merged after: https://github.com/google/gvisor-website/pull/77 or https://github.com/google/gvisor-website/pull/78 PiperOrigin-RevId: 253132620
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