go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Nicolas Lacasse 30c20df76f Run gentdents_benchmark with fewer files. 
This test regularly times out when "shared" filesystem is enabled.

PiperOrigin-RevId: 329950622
 		2020-09-03 10:54:01 -07:00
..
benchmarks Add Docs to nginx benchmark. 2020-09-02 11:22:17 -07:00
cmd/test_app Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
e2e Mark integration tests as passing in VFS2 except CheckpointRestore. 2020-08-11 10:37:32 -07:00
fuse Merge pull request #3250 from craig08:fuse-getattr 2020-08-12 14:36:04 -07:00
image Add standard entrypoints for test targets. 2020-07-20 18:05:05 -07:00
iptables Speed up iptables tests 2020-08-10 17:50:01 -07:00
packetdrill Add bzl_library rules for .bzl files without one. 2020-08-06 12:10:49 -07:00
packetimpact Avoid grpc_impl 2020-09-03 05:52:17 -07:00
perf Run gentdents_benchmark with fewer files. 2020-09-03 10:54:01 -07:00
root Add nogo support to go_binary and go_test targets. 2020-08-25 12:18:25 -07:00
runner Run syscall tests in uts namespaces. 2020-08-31 11:58:45 -07:00
runtimes [runtime tests] Exclude flaky nodejs test 2020-09-02 11:13:02 -07:00
syscalls Fix Accept to not return error for sockets in accept queue. 2020-09-02 18:21:47 -07:00
uds
…
util Refactor tty codebase to use master-replica terminology. 2020-09-01 14:43:41 -07:00
BUILD
…
README.md Fix typos in test/README.md. 2020-06-17 09:13:09 -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_tests.sh

To run root tests, run:

./scripts/root_tests.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.