go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Ghanan Gowripalan 955e09dfbd Do not send to the zero port 
Port 0 is not meant to identify any remote port so attempting to send
a packet to it should return an error.

PiperOrigin-RevId: 341009528
 		2020-11-06 01:47:09 -08:00
..
benchmarks Add parsers golang benchmarks. 2020-10-09 14:29:21 -07:00
cmd/test_app
…
e2e [testing] Use container address to talk to server running inside container. 2020-09-17 17:58:08 -07:00
fuse Fix kernfs unlinkat and rmdirat incorrect resolved path name 2020-09-17 21:07:12 +00:00
image [testing] Use container address to talk to server running inside container. 2020-09-17 17:58:08 -07:00
iptables iptables testing: handle EINTR on calls to accept(). 2020-10-23 16:13:01 -07:00
kubernetes Add gvisor webhook configuration 2020-10-09 17:11:19 -07:00
packetdrill Add bzl_library rules for .bzl files without one. 2020-08-06 12:10:49 -07:00
packetimpact Make the regex for inet6Line in packetimpact/netdevs more accurate 2020-11-04 18:19:44 -08:00
perf Run gentdents_benchmark with fewer files. 2020-09-03 10:54:01 -07:00
root Fix failure setting OOM score adjustment 2020-11-05 15:36:20 -08:00
runner Block external network for tests 2020-11-02 10:41:52 -08:00
runtimes [runtime tests] Add partitions to runtime tests. 2020-11-05 17:11:32 -08:00
syscalls Do not send to the zero port 2020-11-06 01:47:09 -08:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util Merge pull request #4543 from lubinszARM:pr_test_sigaltstack 2020-10-28 08:00:34 -07:00
BUILD
…
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.