ee458c3c50
Right now, cached updates generated during "check" policy runs are completely decoupled from upgrade operations. This can lead to the surprising situation where the "Available update" is *older* than a freshly deployed pending tree with `rpm-ostree upgrade`. We should just generate a cached update after upgrade operations. This is also prep for staged deployments, where we'll want to do this as well. Note that we write out the cached update here even if automatic updates are turned off since it's essentially free. I've been thinking about always displaying that information after an `rpm-ostree upgrade` in `status`. Though not sure if we should keep it in a separate "Available update" section, or somehow morph it as part of the pending deployment output. Closes: #1344 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.