go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Michael Pratt 98f7fbb59f Load C++ rules from @rules_cc 
See https://github.com/bazelbuild/bazel/issues/8743. This will be required in
Bazel 1.0.

Protobuf was updated in
bf0c69e130 (diff-96239ee297e0a92ac6ff96a6bc434ef0).

GoogleTest was updated in
6fd262ecf7.

gflags has not yet been updated, so the repo still won't build with
--incompatible_load_cc_rules_from_bzl.

Tested with buildifier -warnings=native-cc -lint=warn **/BUILD.

PiperOrigin-RevId: 267638515
 		2019-09-06 11:29:00 -07:00
..
e2e Impose order on test scripts. 2019-09-03 22:02:43 -07:00
image Impose order on test scripts. 2019-09-03 22:02:43 -07:00
root Ignore the root container when calculating oom_score_adj for the sandbox. 2019-09-05 19:21:25 -07:00
runtimes Impose order on test scripts. 2019-09-03 22:02:43 -07:00
syscalls Load C++ rules from @rules_cc 2019-09-06 11:29:00 -07:00
util Load C++ rules from @rules_cc 2019-09-06 11:29:00 -07:00
BUILD Bump Bazel to v0.28.0 2019-08-13 11:21:55 -07:00
README.md Impose order on test scripts. 2019-09-03 22:02:43 -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.
  • util: utilities library to support the tests.

For the above noted cases, the relevant runtime must be installed via runsc install before running. This is handled automatically by the test scripts in the kokoro directory.