go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Bhasker Hariharan b69352245a Fix Accept to not return error for sockets in accept queue. 
Accept on gVisor will return an error if a socket in the accept queue was closed
before Accept() was called. Linux will return the new fd even if the returned
socket is already closed by the peer say due to a RST being sent by the peer.

This seems to be intentional in linux more details on the github issue.

Fixes #3780

PiperOrigin-RevId: 329828404
 		2020-09-02 18:21:47 -07:00
..
benchmarks
…
cmd/test_app
…
e2e Mark integration tests as passing in VFS2 except CheckpointRestore. 2020-08-11 10:37:32 -07:00
fuse Merge pull request #3250 from craig08:fuse-getattr 2020-08-12 14:36:04 -07:00
image Add standard entrypoints for test targets. 2020-07-20 18:05:05 -07:00
iptables Speed up iptables tests 2020-08-10 17:50:01 -07:00
packetdrill Add bzl_library rules for .bzl files without one. 2020-08-06 12:10:49 -07:00
packetimpact Fix handling of unacceptable ACKs during close. 2020-09-01 17:45:04 -07:00
perf
…
root Add nogo support to go_binary and go_test targets. 2020-08-25 12:18:25 -07:00
runner
…
runtimes
…
syscalls Fix Accept to not return error for sockets in accept queue. 2020-09-02 18:21:47 -07:00
uds
…
util Refactor tty codebase to use master-replica terminology. 2020-09-01 14:43:41 -07:00
BUILD
…
README.md
…

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.