This adds another new fifloader-only top-level concept,
ProductDefaults. This just contains default values for all
products (on a per-file basis; these are applied *before* file
merge happens).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I noticed that products with the same flavor often repeat the
same settings. Let's use our intermediate format to reduce this
repetition. We'll add a top-level dict for Flavors which allows
them to have settings, then in reverse_qol, for each product,
merge in the flavor's settings. Conflicts are resolved in favor
of the product.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I saw a case where line 1 had a cursor visible so the match
failed. Instead of having two needles for cursor / no cursor,
let's just match on lines 2 and 3 instead so it's not a problem.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We will fix that test upstream but for now skip it to prevent false
positives on all future kernel updates.
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
This is a change in the image viewer app, or maybe fallout from
the menu_launch_type change, not sure. Anyhow, it's not really
a problem if the image viewer opens in a small window rather than
maximized, so let's just have a needle for it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is how the test did it before the big menu_launch_type
commit, and we use 'kwallet' in another test. Doing this needs an
additional needle or needle tag, which is pointless, let's just
be consistent that it's 'kwallet'.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We have enhanced the menu_launch_type to allow for
start checking and maximizing applications.
This PR uses the new functions wherever it seems
logical.
If special logic was used for certain cases,
we have not touched these to preserve the
exact behaviour.
The crash workaround for the Fonts flatpak is dropped because it
no longer seems to be needed with the latest version of the
flatpak, and dropping it simplifies this migration.
Fixes: https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/358
It seems like 480 is a bit low for our oldest, slowest x86_64
worker hosts on the lab instance (worker03 and worker05), they
frequently hit this and fail. Let's bump it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Fedora Rawhide (to be 43) has new applications that replace
the older ones, namely Papers replacing Evince and Showtime
replacing the Totem.
We are adding a condition to run correct applications on Rawhide
while retaining the older applications for a while until the change
has been made in whole.
Fixes: https://pagure.io/fedora-qa/os-autoinst-distri-fedora/issue/375
This seems to be sometimes *causing* problems now. In some cases,
the first launch actually worked but we don't wait long enough
for anaconda to show up, so we launch it twice, and that can
cause failures like https://bugzilla.redhat.com/2360859 .
I did a dry run for a few days on staging and just dropping the
loop entirely didn't seem to produce any failures-to-launch, so
maybe the various bugs we added this for in the first place have
all gone away? Let's try dropping it. If we run into failure-to
-launch problems again, we can add it back but bump the timeout
or something.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
In two cases we don't need separate needles for identifying a
screen and then clicking something on it: we can just also use
the thing-to-click for identification purposes. Also remove the
connect_button-verify needle which has never matched (it matches
on the Verify button but has the tag for the Connect button, no
idea why), and update all the needles for the new GNOME fonts.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Oh, no particular reason or anything. *ahem*
https://bugzilla.redhat.com/2358785
This should cover a decent range of transient bootable media,
ensuring the UEFI fallback mechanism doesn't kick in if you're
just booting the installer or live environment.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Today it has a much more KDE-y window appearance, without bold
titles. Not sure why it's different from yesterday, but never
mind.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
There's now a header bar in fullscreen mode which appears until
you move the mouse away from it, and screws up the needle match.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Sometimes the clock is at 14:38 not 14:37 when we hit this point
in the test, so we need two needles. The 14:38 one hadn't been
updated for the new font yet.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This got messed up in 1e6da7019c
where the KDE needles all got renamed to apps_run_abrt* and their
tags changed to apps_run_abrt, but the KDE *test* was not changed
to look for apps_run_abrt instead of abrt_runs, so we wound up
creating a whole new bunch of abrt_runs needles so we had *three*
sets of needles...
This rationalizes it down to the needles that actually match in
current tests, properly renames them all to apps_run_abrt and
updates the KDE test to look for that tag, and adds a couple of
new needles for the recent downgrade of the app.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The image changes size a bit depending on changes to the text,
I think that's why we always need a variant of this at release
time.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I think it should be OK to do this without any fancy conditions.
It'll fail for F41 respins, but eh. May fail for F42 nightlies
until we push the update stable.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Trying to fix the frequent failures of this test, still. I don't
think we need the loop if we make sure to select the *parent*
entry in the list, which the needle tweaks should ensure, but
we might need to click twice to ensure it's selected and not
delete the entire btrfs volume by mistake, which is what we keep
doing.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
