gvisor/test
Arthur Sfez b4357939c0 Re-enable ipv4 reassembly packetimpact tests
When these specific tests were first added, they would fail when ran by
kokoro during the presubmit tests (but they always passed locally).
These tests are now passing, so they can be re-enabled. Unclear what
changed, one hypothesis is the move from kokoro to buildkite.

Fixes #4971

PiperOrigin-RevId: 354425395
2021-01-28 16:54:24 -08:00
..
benchmarks Fix minor typos 2021-01-13 09:51:38 -08:00
cmd/test_app Fix simple mistakes identified by goreportcard. 2021-01-12 12:38:22 -08:00
e2e Deflake TestBindOverlay in //test/e2e:integration_test 2020-12-29 20:24:40 -08:00
fsstress Fix fsstress argument name 2021-01-21 13:20:52 -08:00
fuse fs/fuse: check that a task has a specified file descriptor 2021-01-05 09:47:30 -08:00
image [testing] Use container address to talk to server running inside container. 2020-09-17 17:58:08 -07:00
iptables iptables: support matching the input interface name 2021-01-21 23:19:19 -08:00
kubernetes Add gvisor webhook configuration 2020-10-09 17:11:19 -07:00
packetdrill Refactor the Makefile to avoid recursive Make. 2020-12-09 15:53:23 -08:00
packetimpact Re-enable ipv4 reassembly packetimpact tests 2021-01-28 16:54:24 -08:00
perf Support partitions for other tests. 2020-12-03 01:00:21 -08:00
root Switch uses of os.Getenv that check for empty string to os.LookupEnv. 2021-01-13 15:15:20 -08:00
runner Support TEST_PREMATURE_EXIT_FILE in syscall tests 2021-01-15 13:03:58 -08:00
runtimes Internal change. 2020-12-17 14:05:01 -08:00
syscalls Add O_PATH support in vfs2 2021-01-28 12:24:37 -08:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util Add O_PATH support in vfs2 2021-01-28 12:24:37 -08:00
BUILD Standardize on tools directory. 2020-01-27 12:21:00 -08:00
README.md Remove unused scripts. 2020-09-23 17:38:02 -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:

make docker-tests

To run root tests, run:

make root-tests

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.