History

Fabricio Voznika 29cd05a7c6 Add sandbox to cgroup Sandbox creation uses the limits and reservations configured in the OCI spec and set cgroup options accordinly. Then it puts both the sandbox and gofer processes inside the cgroup. It also allows the cgroup to be pre-configured by the caller. If the cgroup already exists, sandbox and gofer processes will join the cgroup but it will not modify the cgroup with spec limits. PiperOrigin-RevId: 216538209 Change-Id: If2c65ffedf55820baab743a0edcfb091b89c1019		2018-10-10 09:00:42 -07:00
..
image	Capture boot panics in debug log.	2018-10-04 11:01:44 -07:00
integration	Add sandbox to cgroup	2018-10-10 09:00:42 -07:00
root	Add tests to verify gofer is chroot'ed	2018-10-09 21:07:14 -07:00
testutil	Add sandbox to cgroup	2018-10-10 09:00:42 -07:00
README.md	Fix sandbox chroot	2018-10-03 20:44:20 -07:00
install.sh	Created runsc and docker integration tests.	2018-07-11 09:37:28 -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.

integration: defines integration tests that uses docker run to test functionality.
image: basic end to end test for popular images.
root: tests that require to be run as root.
testutil: utilities library to support the tests.

The following setup steps are required in order to run these tests:

 `./runsc/test/install.sh [--runtime <name>]`

The tests expect the runtime name to be provided in the RUNSC_RUNTIME environment variable (default: runsc-test). To run the tests execute:

bazel test --test_env=RUNSC_RUNTIME=runsc-test \
  //runsc/test/image:image_test \
  //runsc/test/integration:integration_test