go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Bhasker Hariharan 4ee64a248e Fix for panic in endpoint.Close(). 
When sending a RST on shutdown we need to double check the
state after acquiring the work mutex as the endpoint could
have transitioned out of a connected state from the time
we checked it and we acquired the workMutex.

I added two tests but sadly neither reproduce the panic. I am
going to leave the tests in as they are good to have anyway.

PiperOrigin-RevId: 292393800
 		2020-01-30 12:00:35 -08:00
..
e2e Standardize on tools directory. 2020-01-27 12:21:00 -08:00
image Standardize on tools directory. 2020-01-27 12:21:00 -08:00
iptables Fix iptables tests that were broken by rename. 2020-01-29 16:27:12 -08:00
root Standardize on tools directory. 2020-01-27 12:21:00 -08:00
runtimes Standardize on tools directory. 2020-01-27 12:21:00 -08:00
syscalls Fix for panic in endpoint.Close(). 2020-01-30 12:00:35 -08:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util Prefer Type& over Type & 2020-01-28 11:18:17 -08:00
BUILD Standardize on tools directory. 2020-01-27 12:21:00 -08: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.