7911b14f49
The `cached-update` variant would mark a bunch of RPMs as upgraded even if they didn't actually change. The issue turned out to be we were doing the diff all wrong in the staged deployment case. I'm not sure what I was thinking in #1344, but essentially, we were marking all layered RPMs in the staged deployment as updates instead of only marking those layered RPMs which were actually changed EVR. We just simplify the approach here by directly doing a pkglist diff between the booted and staged deployments and consuming that. That's really all there is to it! Reduces the code quite a bit too. Closes: #1446 Closes: #1455 Approved by: cgwalters |
||
|---|---|---|
| .. | ||
| check | ||
| common | ||
| compose-tests | ||
| composedata | ||
| ex-container-tests | ||
| gpghome | ||
| manual | ||
| utils | ||
| vmcheck | ||
| compose | ||
| ex-container | ||
| README.md | ||
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.