Commit Graph

9 Commits

Author SHA1 Message Date
Adam Williamson 06bfd2d2ae Make the update non-matching package check smarter
With Rawhide updates, we quite often run into a situation where
a test runs after a *later* version of the package has already
gone stable. This even happens for stable releases too, though
less often. The current shell-based check just always fails on
this case, but it's usually OK, and manually marking every case
like this with an "it's OK!" comment gets tiring. Instead, let's
use a smarter Python script to do the check. We compare the EVR
of all installed update packages with the EVR of the package
from the update. If it's the same, fine. If the installed package
is lower-versioned, that's always an error, and we fail. If the
installed package is higher-versioned, we check whether the
update already went stable. If it did, then we soft fail, because
probably nothing can go wrong at this point (this is the usual
Rawhide case). If the update did not yet go stable, we still
hard fail, because something can go wrong in this case: if the
update *now* goes stable, the older version from the update may
be tagged over the newer version the test got (presumably from
current stable).

If anything goes wrong with the Bodhi check, or the test is
running on a task not an advisory, we treat both cases as fatal.

The script also gives easier-to-understand output than the old
approach, which should be a bonus.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2023-01-31 10:14:45 -08:00
Adam Williamson 74a27bcee7 Update comparison branch for tox
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2022-07-12 16:15:32 -07:00
Adam Williamson 57789300c5 CI: use fedora-latest-container nodeset
We don't need a VM, container should be fine, and 'latest' means
we don't have to keep bumping this as new releases come out.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2021-11-18 15:25:53 -08:00
Adam Williamson 138ca2bcf6 CI config: update to Fedora 35 and add Python 3.10
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2021-11-12 12:23:54 -08:00
Dan Čermák 5ed8e33b75
Specify branch to compare for diff-cover
diff-cover now compares by default against origin/main, but the main branch is
origin/master which makes the Zuul pipeline fail.
2021-07-21 11:02:03 +02:00
Adam Williamson 21eea18562 Add a needle check script, remove some unused needles
I call this...The @lruzicka Catcher!

It's a script that checks for needles that aren't actually used
anywhere. It also checks for cases where we have a needle JSON
file but no image, or an image file but no JSON file (and wipes
one case of the latter). It also adds a run of the script to tox
so we get it in CI.

You could make this script a lot more elaborate if you like, by
being fancier about parsing the test code and templates, but I
don't think it's really warranted, I think it just needs to be
'good enough'. It's not the end of the world if it misses the
odd thing or the whitelisting goes stale.

Quite a lot of the removed needles are remnants of different
approaches to app start/stop testing which weren't caught in the
initial PR review. The short-name partitioning ones are odd; they
were introduced in the commit that moved needles into subdirs,
but at least some of them don't actually appear to be moves. They
may have been non-tracked files Josef had lying around that got
into the commit by mistake, or they may just be old needles we
really used at some point but aren't using any more.
reclaim_space_second_partition was introduced as part of the
shrink test (along with reclaim_space_first_partition) but was
never actually used by that test - I guess, again, the test got
re-written during review but we forgot to remove the needle. We
rejigged user creation to use tab presses not a needle match a
while back, which made user_creation_password_input unnecessary.
The various cockpit_updates_* needles are I think remnants of
rewrites of the cockpit update tests that again were missed in
PR review, the tests as merged never used them.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-04-08 16:55:46 -07:00
Adam Williamson dce733d186 Re-enable py39 in tox config
diff-cover merged my PR and cut a release, so I hope this should
work again.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-04-08 11:47:06 -07:00
Adam Williamson e2fdf125b2 tox: disable py39 environment until diff-cover is fixed
diff-cover is broken on Python 3.9:
https://github.com/Bachmann1234/diff_cover/pull/140
once that is fixed we can re-enable this.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-04-07 12:20:50 -07:00
Adam Williamson 214f2cc8eb Add fifloader tests, template schemas, update README
This adds a test suite for fifloader (renamed fifloader.py for
test sanity). It adds JSON Schema form schemas for both FIF and
upstream openQA template data, and has fifloader (optionally,
but by default) validate both input and output data against the
schemas. It also adds a tox.ini configured to run the fifloader
tests, use fifloader to validate the template files, and do diff
coverage and lint checks. It also adjusts the Zuul config to run
tox instead of the test job.

There are also some pylint cleanups, since the new tests run
pylint.

fifcheck, fifconverter and tojson.pm are removed, as they were
mainly only needed for one-time conversion of the old format
templates; now they are in the git history we can always recover
them if we need them.

Along with all this I updated the README a bit to explain some
of it (and explain FIF better), and to explicitly state that this
repo is GPLv2+ licensed, and added GPL headers to some of the
files.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2020-01-29 22:45:38 -08:00