gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-07-31	[runtime tests] Enhance java runtime test.	Ayush Ranjan
	- Added a bunch of helpful options which help in speeding up the test and providing useful output. - Unexcluded passing tests and updated bugs. Excluded tests which were failing. - Increased the batch size for java tests so that we can take advantage of the shared JVMs. The running time of the tests decreased from 3+ hours (I don't know the exact running time because this test has always timed out after 3 hours) to 1 hour 15 minutes. We can reliably run this a CI kokoro job. PiperOrigin-RevId: 324301503
2020-07-28	[Runtime Tests] Exclude flaky/failing tests	Ayush Ranjan
	PiperOrigin-RevId: 323632510
2020-07-17	Automated rollback of changelist 321647645	Ayush Ranjan
	PiperOrigin-RevId: 321808673
2020-07-16	Port runtime tests to use go_test	Ayush Ranjan
	PiperOrigin-RevId: 321647645
2020-07-11	Runtime test batch executor	Ayush Ranjan
	Earlier we were docker exec-ing each test at a time. However invoking the test framework has a fixed overhead which made it infeasible to make the runtime tests run as presubmits. This change now executes tests in batches of 50 (can be altered). This really speeds up testing process. With this change, the following tests can be run in reasonable times: - Go - Nodejs - Php - Python PiperOrigin-RevId: 320763916
2020-06-15	Remove blacklist from //test/runtimes	Michael Pratt
	Updates #2972 PiperOrigin-RevId: 316534165
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-01-27	Standardize on tools directory.	Adin Scannell
	PiperOrigin-RevId: 291745021
2019-10-30	Add Kokoro config for new runtime tests	Brad Burlage
	PiperOrigin-RevId: 277607217
2019-10-09	Add blacklists for remaining runtime tests, and test that they parse correctly.	Nicolas Lacasse
	PiperOrigin-RevId: 273781112
2019-10-01	Add blacklist support to the runtime test runner.	Nicolas Lacasse
	Tests in the blacklist will be explicitly skipped (with associated log line). Checks in a blacklist for the nodejs tests. PiperOrigin-RevId: 272272749
2019-09-18	Shard the runtime tests.	Nicolas Lacasse
	Default of 20 shards was arbitrary and will need fine-tuning in later CLs. PiperOrigin-RevId: 269922871
2019-09-03	Impose order on test scripts.	Adin Scannell
	The simple test script has gotten out of control. Shard this script into different pieces and attempt to impose order on overall test structure. This change helps lay some of the foundations for future improvements. * The runsc/test directories are moved into just test/. * The runsc/test/testutil package is split into logical pieces. * The scripts/ directory contains new top-level targets. * Each test is now responsible for building targets it requires. * The install functionality is moved into `runsc` itself for simplicity. * The existing kokoro run_tests.sh file now just calls all (can be split). After this change is merged, I will create multiple distinct workflows for Kokoro, one for each of the scripts currently targeted by `run_tests.sh` today, which should dramatically reduce the time-to-run for the Kokoro tests, and provides a better foundation for further improvements to the infrastructure. PiperOrigin-RevId: 267081397
2019-07-29	Move runtimes tests to appropriate directory.	Samantha Sample
	PiperOrigin-RevId: 260577765