dnf5 needs us to do this to make it use the repo config from the
host, rather than expecting there to be one inside the target
install root. This test should now always run on F41 with dnf5,
so let's just change it unconditionally.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
See https://bugzilla.redhat.com/show_bug.cgi?id=2324231 - since
the port to Wayland, the entry we need in the filesystem list is
not visible at first, we need to scroll the list to find it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It's not just Installation Destination, on aarch64 at least we
have lots of tests failing because entering the source or software
selection spokes didn't work. Let's try extra clicks for these
too.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Dunno why this changed again, but now it's grey and with a
slightly different but still wrong icon.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Recent F40 respin tests hit several failures due to differences
in apperance to Rawhide, here's the fixes.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It seems Maps now shows an indicator on the map when you search
for a place, which threw off a lot of needles.
Also the place info boxes seem to all be broken, I'll file that
when I get around to it.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
I am honestly not sure exactly when we hit this needle, but we
did at least once, and it's mentioned in the comment in the test.
Huh.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
In tests of the Rawhide anaconda update that ports to Wayland,
we often hit failures because the first attempt to click on
Installation Destination doesn't work. This only happened on prod
(not staging), it didn't happen every time (but quite often), and
we can't reproduce it manually, so it seems like a weird glitch
that we should just work around. Simply waiting a second and
clicking again seems to do the job, and should be safe even if
the first click works (the second click will just be on an empty
area of the Installation Destination screen, unless we have like
eight disks attached).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
All the KDE flakiness lately is likely caused by the recurrence
of https://bugzilla.redhat.com/show_bug.cgi?id=2312900 , which
came back because the patch to fix it was inadvertently dropped.
This adds the F40 and F41 updates that re-introduce the patch as
workarounds to address the sluggishness.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
The others have all been rebased to F41, so we had to bump the
Platform version to 41, but since Cheese is kinda dead these
days, its flatpak hasn't been bumped, and that makes building
the F39 ostree installer image fail. To work around this, sed
it out of the pungi config.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We do a menu_launch_type for kwalletmanager, so we'd better keep
a doublek workaround before that :/
Signed-off-by: Adam Williamson <awilliam@redhat.com>
These seem to be needed as a consequence of the previous commit
changes to desktop_login, not sure why, maybe something to do
with no longer opening the kicker once before we start doing
power actions.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Also be a bit more consistent about asserting we saw a terminal
and waiting a bit before typing stuff. We can drop the doublek
workarounds from the keyring tests as we no longer use the
kicker to launch the terminal on KDE (we use ctrl-alt-t shortcut).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This started out as just factoring out the repeated pattern for
launching a terminal on the desktop that came in with the i3
tests. But as I worked on desktop_login, which is a major user
of it, I noticed some potential cleanups and improvements in the
user switching stuff, and also realized we can turn that test
back on for KDE now - user switching was re-enabled in KDE a year
ago and is advertised to be reliable.
I don't think the "switch user from a lock screen" test fully
worked before, as we did not verify that we'd really switched
back to an existing session rather than starting a new one. Now
we do. Using the terminal to verify the logged-in user on all
desktops just keeps things simpler than using the kicker menu
on KDE (though if typing proves unreliable on KDE I may switch
this back).
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Without this, all we did on i3 was hit alt-d and...do nothing,
we didn't type the app name.
I was confused at how we didn't notice this before, but it looks
like at present menu_launch_type isn't actually used in any
test we run on i3 (a lot of tests that use it to run a terminal
got a branch for i3 which uses alt-enter instead). This is an
obvious landmine, though, and it caused things to look weird
when rebasing #323 (which is how I noticed the bug).
This also refactors the sub to use the same logic for all
desktops, just with a different key for i3, since they really
all work the same. i3 doesn't need as much waiting as the other
desktops, probably, but it doesn't really hurt and keeps the code
simple.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We seem to be having quite a few failures lately because the
viewer window in KDE never got maximized. This makes us a bit
more conservative at startup and puts the maximization / sentence
check in a send_key_until_needlematch loop to give it more
chances.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
There's no obvious reason we're not also running these tests on
updates, so let's do it. We have to skip the advisory and UEFI
post checks for desktop_login as the last step of that test is
shutting down the system.
We leave out desktop_login for now because of
https://gitlab.gnome.org/GNOME/gjs/-/issues/647
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This avoids some magic waits by asserting screens (which is much
more reliable), and combines KDE and GNOME flows in the
passwordless test by adding some needle tags to the nautilus
needles.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
