732e0f232a
The refspec code really needs to be cleaned up and oxidized (and unit tested more). The original intention is that if you're pinned to a commit, we say "No upgrade available" but we were crashing if one (understandably) rebased to the combination of `remote:checksum` instead of just `checksum`. But, we can't change the classifier to call this `CHECKSUM` and output an error, because that just conflicts with us accepting the syntax `rpm-ostree rebase :<checksum>`. I'm actually coming around to the idea that this `remote:checksum` syntax means "no upgrade available" is correct, whereas pinning to just `checksum` is more of an error when you try to upgrade. Closes: https://github.com/coreos/rpm-ostree/issues/2603 |
||
|---|---|---|
| .. | ||
| 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.