Ideally, the prepare phase of the downgrade test would do the same, i.e.
first remove package, then try to install the old one and if that fails, skip the test, otherwise update to the new package.
But that'd be 3 operations (remove, install, update) more than what we do now for every package just for a very rare use-case (old package can't be installed).
Now the prep-downgrade does nothing because the previous (update) test leaves the new package installed.
Also, have separate exit code for skipped tests so that we can distinguish them in the viewer.
https://pagure.io/fedora-ci/general/issue/382 https://gitlab.com/testing-farm/oculus/-/issues/18
Ideally, the prepare phase of the downgrade test would do the same, i.e. first remove package, then try to install the old one and if that fails, skip the test, otherwise update to the new package. But that'd be 3 operations (remove, install, update) more than what we do now for every package just for a very rare use-case (old package can't be installed). Now the prep-downgrade does nothing because the previous (update) test leaves the new package installed.
Also, have separate exit code for skipped tests so that we can distinguish them in the viewer.