mirror of https://github.com/linuxkit/linuxkit.git synced 2025-12-01 14:52:41 +00:00

Files

Dave Tucker ce2bdea399 Add a test suite ✅

This adds a test suite to be executed using `linuxkit/rtf`.
This is installed in the top-level Makefile

The tests are written in shell script and cover the following cases:

- Kernel Config is OK!
- Kernel Modules can be built and loaded
- QEMU can build and run kernel+initrd, iso-bios and iso-uefi
- That we can build for all other supported output formats
- That all of the examples in `./examples` can be built
- The LTP tests can be run (if `-l slow` is provided)

The virtsock and docker-bench tests were migrated but no test has been
written as yet as AFAICT they are still a WIP

Signed-off-by: Dave Tucker <dt@docker.com>

2017-05-12 20:12:59 +01:00

cases

Add a test suite ✅

2017-05-12 20:12:59 +01:00

pkg

tests: Update virtsock stress test commit

2017-05-10 13:32:48 +01:00

.gitignore

Add a test suite ✅

2017-05-12 20:12:59 +01:00

Makefile

Add a test suite ✅

2017-05-12 20:12:59 +01:00

README.md

Add a test suite ✅

2017-05-12 20:12:59 +01:00

README.md

Linuxkit Tests Labels

Usage of Artifacts vs Temporary Directory

As the Build Machines have no secrets they will not be able to test running the build output on any cloud providers. In this instance, the build tests should copy their output to the LINUXKIT_ARTIFACTS_DIRECTORY

Labels

The gcp label is applied when the system where the tests are being run meets the requirements for using Google Cloud Platform.

These requirements are:

The system has the necessary CLOUDSDK_* environment variables exported
The system has either keys for a GCP service account or is able to use application default credentials

The packet.net label is applied when a system is able to create machines on Packet.net

The vmware label is used when the machine has VMware Workstation or Fusion installed