go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Arthur Sfez 6c1237da03 Reply to invalid ACKs even when accept queue is full 
Before checking if there is space in the accept queue, the listener
should verify that the cookie is valid. If it is not, instead of
silently dropping the packet, reply with an RST.

Fixes #6683

PiperOrigin-RevId: 400807346
 		2021-10-04 13:57:27 -07:00
..
benchmarks Pass address properties in a single struct 2021-09-15 15:00:01 -07:00
cmd/test_app Rename go files that contain "main" function to main.go. 2021-06-09 17:36:51 -07:00
e2e Support RTM_DELLINK 2021-07-30 15:41:36 -07:00
fsstress Add fsstress test to goferfs 2021-07-20 22:21:24 -07:00
fuse Disable all tests dependent on cloud_gvisor::testing::FuseTest. 2021-06-10 15:54:34 -07:00
image Fail tests when container returns non-zero status 2021-04-05 11:39:53 -07:00
iptables iptables: support postrouting hook and SNAT target 2021-04-09 21:11:26 -07:00
kubernetes Add gvisor webhook configuration 2020-10-09 17:11:19 -07:00
packetdrill Clean test tags. 2021-04-20 13:11:25 -07:00
packetimpact Reply to invalid ACKs even when accept queue is full 2021-10-04 13:57:27 -07:00
perf Deflake test/perf:randread_benchmark 2021-08-17 12:58:37 -07:00
root Merge pull request #6292 from btw616:local-timezone 2021-07-26 16:47:13 -07:00
runner Internal change. 2021-09-11 18:04:15 -07:00
runtimes Replace whitelist with allowlist 2021-07-13 17:20:41 -07:00
syscalls Merge pull request #6551 from sudo-sturbia:msgqueue/procfs 2021-10-01 12:04:17 -07:00
uds [op] Replace syscall package usage with golang.org/x/sys/unix in test/. 2021-03-06 09:54:09 -08:00
util Allow creating packet socket bound to any protocol 2021-09-16 20:06:26 -07: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.