go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Ting-Yu Wang 7c118f7e19 KVM platform does not support 32bit. 
Fixes: //test/syscalls:32bit_test_runsc_kvm
Ref change: 5d569408ef
PiperOrigin-RevId: 292563926
 		2020-01-31 10:07:45 -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 Simplify testing link rules. 2020-01-30 17:49:17 -08:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util KVM platform does not support 32bit. 2020-01-31 10:07:45 -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.