2fedc3b0ac
In FCOS, we use "override" lockfiles to pin packages to certain versions. Right now, we have separate overrides for each base arch we (eventually want to) support. But that makes maintaining the overrides cumbersome because of all the duplication. Let's allow lockfiles to specify only the `evr` of a package, which is just as good for FCOS, and means that we'll only have to maintain a single override file for all the architectures. |
||
|---|---|---|
| .. | ||
| check | ||
| common | ||
| compose | ||
| gpghome | ||
| kolainst | ||
| manual | ||
| utils | ||
| vmcheck | ||
| compose.sh | ||
| README.md | ||
| runkola | ||
| vmcheck.sh | ||
Tests are divided into three groups:
-
Tests in the
checkdirectory are non-destructive and uninstalled. Some of the tests require root privileges. Usemake checkto run these. -
The
composechecktests currently require uid 0 capabilities - the default in Docker, or you can run them via a user namespace. They are non-destructive, but are installed.To use them, you might do a
make && sudo make installinside a Docker container.Then invoke
./tests/compose. Alternatively of course, you can simply run the tests on a host system or in an existing container, without doing a build.Note: This is intentionally not a
Makefiletarget because it doesn't require building and doesn't use uninstalled binaries. -
Tests in the
vmcheckdirectory are oriented around using Vagrant. Usemake vmcheckto run them. See alsoHACKING.mdin the top directory.
The common directory contains files used by multiple
tests. The utils directory contains helper utilities
required to run the tests.