go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Bhasker Hariharan a611fdaee3 Changes TCP packet dispatch to use a pool of goroutines. 
All inbound segments for connections in ESTABLISHED state are delivered to the
endpoint's queue but for every segment delivered we also queue the endpoint for
processing to a selected processor. This ensures that when there are a large
number of connections in ESTABLISHED state the inbound packets are all handled
by a small number of goroutines and significantly reduces the amount of work the
goscheduler has to perform.

We let connections in other states follow the current path where the
endpoint's goroutine directly handles the segments.

Updates #231

PiperOrigin-RevId: 289728325
 		2020-01-14 14:15:50 -08:00
..
e2e Deflake TestCheckpointRestore 2019-10-28 18:50:04 -07:00
image Impose order on test scripts. 2019-09-03 22:02:43 -07:00
iptables Fix readme formatting. 2020-01-06 16:49:34 -08:00
root test/root: check that memory accouting works as expected 2019-11-05 17:03:41 -08:00
runtimes Allow all runtime tests for a language to be run via a single command. 2019-11-14 15:06:04 -08:00
syscalls Changes TCP packet dispatch to use a pool of goroutines. 2020-01-14 14:15:50 -08:00
uds Cleanup host UDS support 2019-10-18 15:33:03 -07:00
util Do not consider symlinks as directories in fs utils. 2019-12-10 11:09:44 -08:00
BUILD Bump Bazel to v0.28.0 2019-08-13 11:21:55 -07:00
README.md Add more instructions to test/README.md 2019-10-18 16:18:52 -07:00

README.md

Tests

The tests defined under this path are verifying functionality beyond what unit tests can cover, e.g. integration and end to end tests. Due to their nature, they may need extra setup in the test machine and extra configuration to run.

  • syscalls: system call tests use a local runner, and do not require additional configuration in the machine.
  • integration: defines integration tests that uses docker run to test functionality.
  • image: basic end to end test for popular images. These require the same setup as integration tests.
  • root: tests that require to be run as root. These require the same setup as integration tests.
  • util: utilities library to support the tests.

For the above noted cases, the relevant runtime must be installed via runsc install before running. Just note that they require specific configuration to work. This is handled automatically by the test scripts in the scripts directory and they can be used to run tests locally on your machine. They are also used to run these tests in kokoro.

Example:

To run image and integration tests, run:

./scripts/docker_test.sh

To run root tests, run:

./scripts/root_test.sh

There are a few other interesting variations for image and integration tests:

  • overlay: sets writable overlay inside the sentry
  • hostnet: configures host network pass-thru, instead of netstack
  • kvm: runsc the test using the KVM platform, instead of ptrace

The test will build runsc, configure it with your local docker, restart dockerd, and run tests. The location for runsc logs is printed to the output.