go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Mithun Iyer b645fcd241 Ensure correctness of saved receive window 
When the scaled receive window size > 65535 (max uint16), we advertise
the scaled value as 65535, but are not adjusting the saved receive
window value when doing so. This would keep our current window
calculation logic to be incorrect, as the saved receive window value
is different from what was advertised.

Fixes #4903

PiperOrigin-RevId: 347771340
 		2020-12-16 00:24:28 -08:00
..
benchmarks Fix long running bazel build jobs. 2020-12-11 20:56:09 -08:00
cmd/test_app Remove existing nogo exceptions. 2020-12-11 12:06:49 -08:00
e2e Support icmpv6 transport protocol 2020-12-07 08:44:44 -08:00
fuse Fix error handling on fusefs mount. 2020-12-07 18:00:54 -08:00
image [testing] Use container address to talk to server running inside container. 2020-09-17 17:58:08 -07:00
iptables Remove existing nogo exceptions. 2020-12-11 12:06:49 -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 Ensure correctness of saved receive window 2020-12-16 00:24:28 -08:00
perf Support partitions for other tests. 2020-12-03 01:00:21 -08:00
root Refactor the Makefile to avoid recursive Make. 2020-12-09 15:53:23 -08:00
runner Support partitions for other tests. 2020-12-03 01:00:21 -08:00
runtimes Support partitions for other tests. 2020-12-03 01:00:21 -08:00
syscalls Implement command SEM_INFO and SEM_STAT for semctl. 2020-12-15 16:06:06 -08:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util Skip `EventHUp` notify in `FIN_WAIT2` on a socket close. 2020-11-09 14:54:57 -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.