go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Adin Scannell 6b558bb433 Drop nodejs test that started spontaneously failing. 
It is unclear exactly what happened in the DNS response that has caused
this test to start breaking. However, since this is unrelated to any code
change, this can be attributed to a non-hermetic or broken test case.

See master failure:
https://buildkite.com/gvisor/pipeline/builds/10462#ae46ee7c-855c-4efe-8165-f0c694557cf9

This may be related to https://github.com/nodejs/node/issues/28790, where
older versions of node are not parsing this field correctly? However, we
would like to retain other tests from the same older version of node.

For posterity, the current serial field appears as:

; <<>> DiG 9.17.19-1-Debian <<>> nodejs.org -t SOA +multiline
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56131
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;nodejs.org.            IN SOA

;; ANSWER SECTION:
nodejs.org.             3402 IN SOA meera.ns.cloudflare.com. dns.cloudflare.com. (
                                2264470260 ; serial
                                10000      ; refresh (2 hours 46 minutes 40 seconds)
                                2400       ; retry (40 minutes)
                                604800     ; expire (1 week)
                                3600       ; minimum (1 hour)
                                )

;; Query time: 59 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Thu Dec 09 10:35:57 PST 2021
;; MSG SIZE  rcvd: 102

PiperOrigin-RevId: 415308624
 		2021-12-09 11:17:16 -08:00
..
benchmarks Support STAGED_BINARIES to run prebuilt binaries with the test pipeline. 2021-11-17 17:49:35 -08:00
cmd/test_app
…
e2e Implement ioctl(fd, FIONREAD) for host FDs 2021-11-10 17:07:06 -08: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 Fix typo and bazel output binary path. 2021-11-11 13:12:55 -08: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 Update expectations for generic_dgram_socket_send_recv_test 2021-12-03 18:28:03 -08:00
perf
…
root Merge pull request #6821 from dqminh:feature/cgroupv2 2021-11-29 18:37:42 -08:00
runner
…
runtimes Drop nodejs test that started spontaneously failing. 2021-12-09 11:17:16 -08:00
syscalls Fix socket permission 2021-11-10 15:00:50 -08:00
uds
…
util Allow SetAttr and Allocate for deleted files 2021-11-02 12:29:06 -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:

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.