1
0
mirror of https://pagure.io/fedora-qa/os-autoinst-distri-fedora.git synced 2024-11-27 16:13:09 +00:00
Commit Graph

510 Commits

Author SHA1 Message Date
Adam Williamson
77d6f3128c Use 'fXX-build' tag repo for Rawhide, not 'rawhide'
The 'rawhide' tag repo used to be just a symlink to the 'fXX-build'
one, but With the on-demand repo changes, that's no longer the
case. It looks like the 'fXX-build' repo gets regenerated more
often than 'rawhide' (which seems to regen every two hours), so
let's use 'fXX-build' instead.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-11-07 15:19:40 -08:00
Adam Williamson
b3b39a79d9 Add FEDORA-2024-b3e53a2b43 as workaround for Rawhide
This fixes the systemd-homed service start failure due to SELinux
denial.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-22 08:42:44 -07:00
Adam Williamson
905376e320 Drop workarounds which have gone stable
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-22 08:42:25 -07:00
Adam Williamson
d761df56b2 Add gjs user switch crash fix update as workaround for F41
This should allow us to turn the desktop_login test back on for
updates.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-16 11:01:32 -07:00
Adam Williamson
b4910cee94 Add F40 and F41 kwin sluggishness fix updates as workarounds
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>
2024-10-16 10:57:59 -07:00
Adam Williamson
d194b9d2af Drop a workaround that's already stable
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-16 10:57:26 -07:00
Adam Williamson
e9e967c4bf Consistently use desktop_launch_terminal
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>
2024-10-09 17:19:00 -07:00
Adam Williamson
1f4324b270 abstract desktop terminal launch, refactor user switch, enable for KDE
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>
2024-10-09 17:16:13 -07:00
Adam Williamson
b7487e97e9 Fix menu_launch_type for i3
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>
2024-10-09 11:40:31 -07:00
Adam Williamson
c65071f879 Add ffmpeg 7.0 update as a workaround for F41
It's stable now, and
https://bodhi.fedoraproject.org/updates/FEDORA-2024-8b18ef8dfb
needs it, let's add it as a workaround so we don't have to wait
for a compose.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-05 15:44:52 -07:00
Adam Williamson
52f3897eec Clear existing workarounds, they are all stable now
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-05 15:44:28 -07:00
Adam Williamson
91f4a24b20 Also add FEDORA-2024-cb1e9f47a3 as F41 workaround
The new NetworkManager update needs it. Lack of composes is
starting to bite us more, need to get one through.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-03 12:18:30 -07:00
Adam Williamson
31691a317b Add a higher-NVR build of FreeIPA as a workaround for F42
The freeipa package in F41 got bumped to a higher NVR than the
one in F42, which causes FreeIPA upgrades to fail.

See: https://src.fedoraproject.org/rpms/freeipa/pull-request/22

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-03 10:12:01 -07:00
Adam Williamson
0b5aabcc57 Add FEDORA-2024-e331cd53ac as a workaround for F41
Another update depends on it. It's gone stable already, but we
are having issues with composes ATM so it hasn't made a compose.
It's safe to do this as we can be sure the depended-on update
will be in the next stable compose whenever it completes, so we
can't wind up in an inconsistent state.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-10-02 16:26:17 -07:00
Lukas Ruzicka
092cc5dd05 Move the content from i3 library to the files.
Over the time, we have changed the test scripts so that the code
in the i3.pm library was no more needed. The only leftover was the
user config subroutine that could be moved to the only file that was
using it and we could get rid of the library file.
2024-09-26 16:06:43 -07:00
Lukas Ruzicka
c392480f92 Rebase the PR to fit within the current status quo. 2024-09-26 16:04:59 -07:00
Dan Čermák
4315e5ff6f Add openQA tests for i3 2024-09-26 16:04:59 -07:00
Adam Williamson
82abc61432 Factor DM login process out of _graphical_wait_login
There are several other tests doing the same thing (but not as
safely, in some cases). To improve reliability and reduce
duplication, let's factor this out into utils.pm and reuse it
where appropriate.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-09-26 22:20:34 +00:00
Alessandro Astone
39e26ed029 kde_doublek_workaround: Allow some time for the menu to close 2024-09-15 21:19:18 +02:00
Adam Williamson
358695e417 doublek_workaround: tweak to work for other letters too
In a couple of cases we type something that *doesn't* start with
a 'k', so we should use that other letter for the workaround.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-09-15 11:54:35 -07:00
Adam Williamson
e49b5f9645 Initial ELN update test support (installer build)
This should make the installer image build test work for ELN,
so we can try doing some update tests on ELN.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-09-05 14:57:59 -07:00
Adam Williamson
9a95ece8d3 Clear a now-stable workaround
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-22 11:50:29 -07:00
Adam Williamson
cbb9bb59d4 g-i-s: go back to relnum conditional, update comments
Changing to a conditional based on whether we saw webui broke the
ostree installer install tests, because they of course use the
same g-i-s even though they don't use webui. So, we have to go
back to the relnum-based conditional :/

Yes, this means we have redundant screens in g-i-s for install
paths that use gtkui to deploy GNOME, e.g. SB installer images,
but I can't see a good way to fix that. We need to show those
screens for the live install, which is the 'most important'
one, and we don't have an obvious way to show them for installs
that used webui but hide them for installs that used gtkui.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-20 23:12:29 -07:00
Adam Williamson
76711fd039 Tweak _boot_to_anaconda and g-i-s flow for new Rawhide g-i-s
We're dropping the live user mode patch from g-i-s downstream
because it's just too hard to maintain, apparently. So on Rawhide
the live image will boot to the welcome screen as normal, but
running the installer will give you newui rather than webui. If
you need a language other than English you have to sort it out
at the desktop before running the installer.

On first boot, g-i-s will show *all* screens, not skipping
language, keyboard layout or timezone, because we did not see
those in the installer.

This adapts the tests to handle the new flow, and should still
work with the other flows.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-20 16:15:55 -07:00
Adam Williamson
7379f7636d More updates for webUI deferral to F42
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-18 16:23:13 -07:00
Adam Williamson
3da4f4e8bb Update f41 g-i-s workaround to latest build
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-18 14:13:42 -07:00
Adam Williamson
bd317e001f Add gnome-initial-setup vendor.conf revert update as F41 workaround
This is part of reverting webui for F41. The kickstarts change
is merged, so we need this also.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-18 09:18:48 -07:00
Adam Williamson
175b056ce7 Clear out F41 workarounds list
They're all in stable now.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-18 09:18:16 -07:00
Adam Williamson
89551b72ee Add kde-settings update to workarounds to get f41 bg on KDE
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-16 01:01:10 -04:00
Adam Williamson
d3150edae3 Add tuned to f41 workarounds
To fix base_services_start failures till next compose is done.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-15 22:51:32 -04:00
Adam Williamson
e8ed3a2a96 Add mock-core-configs branched update to F41 workarounds
Looks like it didn't make the compose, or something, we need
this for tests to work.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-15 17:32:12 -04:00
Adam Williamson
6a9ab101bf Remove last vestiges of modularity stuff
This comes with a subtle behavioural change that we no longer
pass --nogpgcheck for upgrade tests, but we didn't really *mean*
to do that for anything but Rawhide, and it *shouldn't* be
necessary for Rawhide now, so let's see if everything is fine
without it.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-14 07:55:24 -04:00
Adam Williamson
fd3a6d1941 Drop a no-longer-needed workaround
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-13 15:27:26 -04:00
Adam Williamson
5132786456 Add 42 to workarounds hash
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-13 15:10:15 -04:00
Adam Williamson
4be9ce3e88 Use 'terminal' instead of 'gnome-terminal' for ptyxis switch
In several places we run 'gnome-terminal' explicitly, but as of
today's compose, the default terminal app on GNOME in Rawhide is
ptyxis, not gnome-terminal.

Running 'terminal' should launch whichever is correct, so let's
consistently do that.

Also, add an apps_run_terminal needle and navigation navbar
needle for ptyxis.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-13 10:39:20 -04:00
Adam Williamson
3f951b47d8 Run update package version check on installer environments
As discussed in https://pagure.io/releng/failed-composes/issue/6538
we noticed a gap in openQA coverage here. We don't check the
versions of packages lorax installs to the installer environment,
and those packages do not make it to the installed system, so if
there's a dep issue that prevents a package in the update from
being included in the installer environment, but the same dep
issue isn't caught on any other path, we miss the problem. This
wires the updvercheck.py script into the _installer_build and
_ostree_build tests to catch this kind of problem, and makes it
capable of parsing pylorax.log files into its preferred format
to enable that.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-08-02 15:10:53 -07:00
Adam Williamson
107d7ce03d Add FEDORA-2024-f86a143437 to workarounds (pd-mapper for F40)
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-07-20 09:24:17 -07:00
Adam Williamson
7945c797fa Remove FEDORA-2024-442827752b and 120746008 from workarounds
Both are stable now.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-07-20 09:23:52 -07:00
Adam Williamson
92ea362578 Add pd-mapper scratch build as workaround
To fix base_services_start always failing on aarch64, while I
wait for review of the upstream and downstream PRs.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-07-19 12:23:47 -07:00
Adam Williamson
0bde610430 Add updated plymouth as workaround for F39
To deal with the UEFI passphrase entry issue, now F39 has kernel
6.9.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-07-10 16:00:58 -07:00
Adam Williamson
51f1654224 Drop 38 from workarounds matrix
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-07-10 16:00:48 -07:00
Adam Williamson
5fda734892 tag/copr updatepkgs.txt generation: filter arches
If the repo has source packages in it, we get a badly-formed
updatepkgs.txt that breaks updvercheck. So let's filter to only
packages of the target arch and noarch.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-06-26 15:16:22 -07:00
Adam Williamson
146e41cca5 Install python3-dnf before running updvercheck.py
...when we're not in an atomic (canned) env, anyway. If we are,
we'll rely on it already being there (as previously ensured by
an earlier commit).

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-06-26 10:56:23 -07:00
Adam Williamson
c8de083f1c Revert "disable_firefox_studies: use SUSE style and add SUSE values"
This reverts commit a3f4a6f2e6. It
seemed to cause *more* annoying bars in Firefox than before, for
some reason, I don't know why. Reverting till I can do more
testing on lab.
2024-06-21 12:46:50 -07:00
Adam Williamson
a3f4a6f2e6 disable_firefox_studies: use SUSE style and add SUSE values
SUSE has a much nicer style for handling all the nested quoting
and stuff in creating the autoconfig files, so switch to that,
and also merge in all the SUSE autoconfig values...the more the
merrier, for making Firefox be less annoying. I'm hoping this
might suppress the "Add a splash of color" modal that's breaking
tests ATM.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-06-21 10:26:57 -07:00
Adam Williamson
e30060218b Drop a workaround that went stable weeks ago
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-06-19 12:53:10 -07:00
Adam Williamson
943c4193d3 Factor out the KDE launcher double-typing workaround, use it more
There's a couple of places where we do menu_launch_type in KDE
without doing this workaround first, and they do run into the
bug sometimes. Let's factor it out from the few places it's
already repeated, and add it to the places it is missing.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-06-11 16:21:00 -07:00
Adam Williamson
304699bc6f Defend even harder against progress spew in updatepkgs.txt
Seems current dnf5 has a bug which causes repository refresh
progress to be sent to stdout even with -q.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-06-11 09:13:01 -07:00
Adam Williamson
670d1072de Yet more timeout
Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-06-11 08:17:22 -07:00
Adam Williamson
e2fde7809c Bump advisory_check timeout even more for really huge "updates"
...well, in this case, the Python side tag, because side tags
that inherit have just *all* the packages in them.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-06-11 00:56:29 -07:00