go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Fabricio Voznika 4b5eae39f2 Enable VFS2 to runsc syscall tests 
Updates #1487

PiperOrigin-RevId: 314271995
 		2020-06-01 23:03:20 -07:00
..
cmd/test_app Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
e2e Fix TestTmpFile 2020-05-21 11:08:10 -07:00
image Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
iptables Fix copied comment mistakes. 2020-05-29 15:39:17 -07:00
packetdrill Standardize all Docker images. 2020-04-24 14:11:42 -07:00
packetimpact Internal change. 2020-06-01 10:41:57 -07:00
perf Deflake //third_party/gvisor/test/perf:getdents_benchmark_runsc_ptrace 2020-04-03 12:29:03 -07:00
root Move Cleanup to its own package 2020-05-28 14:49:06 -07:00
runner Enable VFS2 to runsc syscall tests 2020-06-01 23:03:20 -07:00
runtimes Internal change. 2020-05-05 12:43:28 -07:00
syscalls Enable VFS2 to runsc syscall tests 2020-06-01 23:03:20 -07:00
uds
…
util Add IsRunningWithVFS1 to test util 2020-05-21 10:48:25 -07:00
BUILD
…
README.md
…

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.