go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Zach Koopmans 2ecf66903e Add profiling to dockerutil 
Adds profiling with `runsc debug` or pprof to dockerutil. All
targets using dockerutil should now be able to use profiling.

In addition, modifies existing benchmarks to use profiling.

PiperOrigin-RevId: 323298634
 		2020-07-26 22:02:51 -07:00
..
benchmarks Add profiling to dockerutil 2020-07-26 22:02:51 -07:00
cmd/test_app Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
e2e Add standard entrypoints for test targets. 2020-07-20 18:05:05 -07:00
image Add standard entrypoints for test targets. 2020-07-20 18:05:05 -07:00
iptables iptables: don't NAT existing connections 2020-07-22 16:49:11 -07:00
packetdrill Add standard entrypoints for test targets. 2020-07-20 18:05:05 -07:00
packetimpact Add profiling to dockerutil 2020-07-26 22:02:51 -07:00
perf Internal change. 2020-06-23 14:42:15 -07:00
root Add standard entrypoints for test targets. 2020-07-20 18:05:05 -07:00
runner test/syscall: run each test case in a separate network namespace 2020-07-25 01:04:45 -07:00
runtimes Runtime tests are enormous 2020-07-17 17:19:34 -07:00
syscalls Enable open test 2020-07-24 01:13:06 -07:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util Merge pull request #3165 from ridwanmsharif:ridwanmsharif/fuse-off-by-default 2020-07-15 12:14:42 -07:00
BUILD Standardize on tools directory. 2020-01-27 12:21:00 -08:00
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.