5337ba51b2
These are further fixes based on running more of the rpm-ostree test suite. When dropping the staged deployment, we do need to do the "post operations" such as bumping the sysroot mtime, so that clients know something changed. We also need to regenerate the deployment refs. And of course do a sysroot reload. Also, add a "base cleanup" after creating a staged deployment which also regenerates the refs. Closes: #1570 Approved by: jlebon |
||
|---|---|---|
| .. | ||
| destructive | ||
| nondestructive | ||
| tasks | ||
| README.md | ||
| destructive.yml | ||
| execute_batch.yml | ||
| libinsttest.sh | ||
| libtest-core.sh | ||
| nondestructive.yml | ||
| playbook-run.sh | ||
| provision.sh | ||
| run.sh | ||
README.md
This directory holds tests that use the Fedora Standard Test Interface.
The high level structure is that we take a qcow2 file, inject built RPMs into it, and then use Ansible to run tests.
See .papr.yml for canonical usage.
For local development, you should cache the qcow2 somewhere
stable (outside of this git repo). Also note that ../ci/build-rpms.sh
does not pick up uncommitted changes! Stated more strongly, you
currently need to run build-rpms.sh after every change.
To run just a specific test, use e.g.:
env TEST_SUBJECTS=/path/to/qcow2 ./playbook-run.sh -e tests=.*pull nondestructive.yml