Using cpu=host for this test on our new openQA workers makes it
fail, because mcelog.service doesn't want to run:
Jul 02 21:12:45 fedora mcelog[615]: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead.
this seems like the simplest way to avoid that - let's just run
on a different CPU.
While I'm at it, let's do this more properly for apps_startstop.
It's wrong to hardcode Nehalem at the test level as we may want
to run it on other arches, so make it a variable defined at the
machine level. MINCPU is meant to be "minimum CPU" - a CPU with
baseline capabilities for the arch. For now it's defined as 'host'
on every other machine as I don't know if there is a baseline
qemu CPU model for aarch64 or Power, I'm asking those teams.
Using the same variable for base_services_start is really a bit
of a hack/workaround, but it seems silly to also define MCELOGCPU
or something with the exact same values...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
These are weird needles, but we do occasionally need to do this,
so I figured I'd add them. These are needed if you test an
Everything installer image as "Server-dvd-iso", which can be
useful to run all the former 'universal' tests on such an image.
Several will fail anyway, but a lot will run, if the appropriate
needles are in place.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The install method choices are now hidden until at least one disk
is selected, so we need to match on an interface element that's
always present.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The way side tags work, every package in the distro is in the side
tag repo, so updatepkgs and updatepkgnames end up huge. To fix
this, we'll use a koji query for all packages that are actually in
the side tag to generate updatepkgnames.txt, and then use that to
filter the dnf command to generate updatepkgs.txt.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This doesn't work because the output has the filename in it. We
need just the line count. catting the file to wc achieves that
as now it doesn't know the file name.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Latest Vault doesn't have multiple encryption backends any more,
so there is no indication of the one being used here any more.
Let's just drop the check.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Not quite sure what changed (probably GTK?) but somehow all the
smiley renderings changed a little bit.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It now includes a better explanation of *why* fifloader exists,
and the fundamental design difference between fifloader and both
upstream formats. But to compensate, the other bits are made more
concise, hopefully without losing any useful information.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I've always hated the magic group name derivation in fifloader,
and it prevents it being used by anyone but Fedora. This fixes
that by requiring group_name to be set in the Products. This is
an executive decision, but it makes sense at least with how
Fedora uses openQA. If other users who might want to adopt
fifloader *don't* have a 100% assocation from products to job
groups, we can introduce more ways to set it in future, I guess.
I made it compulsory because it feels weird to have job templates
that aren't in groups...I don't even know how those get shown in
the web UI. But if there's a real use case for this we can make
it optional.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It is required with podman 5.5.0 for the "podman run --device-read-bps"
test. If we don't load it the test will be skipped and we loose some
coverage.
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
This reduces another chunk of duplication in the templates by
using ProfileGroups. It should produce *mostly* the same results
as before, but some inconsistencies are intentionally fixed (like
some desktop tests not running on
fedora-Workstation-upgrade-x86_64-*-64bit), and several priorities
change. It's not really possible to make all priorities match
exactly, so I took the chance to make some more consistent with
our original intent all those years ago: tests related to Basic
criteria should be 20 on blocking images, Beta criteria are 30,
and Final criteria are 40.
We're also consistent about running all the same tests on osbuild
and non-osbuild lives.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
OK, this is getting kinda close to over-engineering, but what
the heck. With this, a profile group can contain another profile
group. There is no infinite recursion protection yet.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Any of the four might not exist. At least *one* of the four has
to exist, but we can't rely on any particular one existing, so we
have to be very defensive. The only rule is that at least one
out of profiles and groups has to exist after merge.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This test suite replaces the Evince test suite and
adds altered scripts and needles to go with the
Papers applications. At the same time, it provides
the same level of functionality and testability
as the original evince test.
Fixes: https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/377
This is another new convenience feature. Groups of profiles let
us avoid repeating commonly-used sets. A test suite can specify
a group of profiles, with a base priority. The priority value
for each profile within the ProfileGroup is added to the base
priority in the test suite.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
They're both using a new PatternFly, so lots of stuff changed.
This is just the update test, we'll have to update a few more
needles for the compose later.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
