af86fcd649
The garbage collection issue should be fixed now, and it's just nicer on developers' cache to stay on the same commit. And again, it's a nice sanity-check to know that we're always able to compose an older tree. That said, we probably should still bump this from time to time. While we're here, add some comments for making it easier to match `popd` calls with the original `pushd`. |
||
|---|---|---|
| .. | ||
| check | ||
| common | ||
| compose | ||
| ex-container-tests | ||
| gpghome | ||
| kola/nondestructive | ||
| manual | ||
| utils | ||
| vmcheck | ||
| compose.sh | ||
| ex-container | ||
| README.md | ||
| 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.