gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2021-06-24	Run `:socket_inet_loopback_isolated_test_linux` tests in a container.	Etienne Perot
	This creates new user and network namespaces for all tests in `:socket_inet_loopback_isolated_test_linux`. PiperOrigin-RevId: 381374120
2021-06-09	Rename go files that contain "main" function to main.go.	Nicolas Lacasse
	This is a good Go convention that we should follow. PiperOrigin-RevId: 378538679
2020-08-06	Add bzl_library rules for .bzl files without one.	Adin Scannell
	PiperOrigin-RevId: 325280924
2020-07-25	test/syscall: run each test case in a separate network namespace	Andrei Vagin
	... when it is possible. The guitar gVisorKernel*Workflow-s runs test with the local execution_method. In this case, blaze runs test cases locally without sandboxes. This means that all tests run in the same network namespace. We have a few tests which use hard-coded network ports and they can fail if one of these port will be used by someone else or by another test cases. PiperOrigin-RevId: 323137254
2020-07-13	Merge pull request #2672 from amscanne:shim-integrated	gVisor bot
	PiperOrigin-RevId: 321053634
2020-04-23	Simplify Docker test infrastructure.	Adin Scannell
	This change adds a layer of abstraction around the internal Docker APIs, and eliminates all direct dependencies on Dockerfiles in the infrastructure. A subsequent change will automated the generation of local images (with efficient caching). Note that this change drops the use of bazel container rules, as that experiment does not seem to be viable. PiperOrigin-RevId: 308095430
2020-02-19	Add basic microbenchmarks.	Adin Scannell
	PiperOrigin-RevId: 296104390