Plan / proposal: enable openQA update testing and potentially
gating on Rawhide updates
by Adam Williamson
Hi folks!
We've had openQA testing of updates for stable and branched releases,
and gating based on those tests, enabled for a while now. I believe
this is going quite well, and I think we addressed the issues reported
when we first enabled gating - Bodhi's gating status updates work more
smoothly now, and openQA respects Bodhi's "re-run tests" button so
failed tests can be re-triggered.
A few weeks ago, I enabled testing of Rawhide updates in the openQA
lab/stg instance. This was to see how smoothly the tests run, how often
we run into unexpected failures or problems, and whether the hardware
resources we have are sufficient for the extra load.
So far this has been going more smoothly than I anticipated, if
anything. The workers seem to keep up with the test load, even though
one out of three worker systems for the stg instance is currently out
of commission (we're using it to investigate a bug). We do get
occasional failures which seem to be related to Rawhide kernel slowness
(e.g. operations timing out that usually don't otherwise time out), but
on the whole, the level of false failures is (I would say) acceptably
low, enough that my current regime of checking the test results daily
and restarting failed ones that don't seem to indicate a real bug
should be sufficient.
So, I'd like to propose that we enable Rawhide update testing on the
production openQA instance also. This would cause results to appear on
the Automated Tests tab in Bodhi, but they would be only informational
(and unless the update was gated by a CI test, or somehow otherwise
configured not to be pushed automatically, updates would continue to be
pushed 'stable' almost immediately on creation, regardless of the
openQA results).
More significantly, I'd also propose that we turn on gating on openQA
results for Rawhide updates. This would mean Rawhide updates would be
held from going 'stable' (and included in the next compose) until the
gating openQA tests had run and passed. We may want to do this a bit
after turning on the tests; perhaps Fedora 37 branch point would be a
natural time to do it.
Currently this would usually mean a wait from update submission to
'stable push' (which really means that the build goes into the
buildroot, and will go into the next Rawhide compose when it happens)
of somewhere between 45 minutes and a couple of hours. It would also
mean that if Rawhide updates for inter-dependent packages are not
correctly grouped, the dependent update(s) will fail testing and be
gated until the update they depend on has passed testing and been
pushed. The tests for the dependent update(s) would then need to be re-
run, either by someone hitting the button in Bodhi or an openQA admin
noticing and restarting them, before the dependent update(s) could be
pushed.
In the worst case, if updated packages A and B both need the other to
work correctly but the updates are submitted separately, both updates
may fail tests and be blocked. This could only be resolved by waiving
the failures, or replacing the separate updates with an update
containing both packages.
All of those considerations are already true for stable and branched
releases, but people are probably more used to grouping updates for
stable and branched than doing it for Rawhide, and the typical flow of
going from a build to an update provides more opportunity to create
grouped updates for branched/stable. For Rawhide the easiest way to do
it if you need to do it is to do the builds in a side tag and use
Bodhi's ability to create updates from a side tag.
As with branched/stable, only critical path updates would have the
tests run and be gated on the results. Non-critpath updates would be
unaffected. (There's a small allowlist of non-critpath packages for
which the tests are also run, but they are not currently gated on the
results).
I think doing this could really help us keep Rawhide solid and avoid
introducing major compose-breaking bugs, at minimal cost. But it's a
significant change and I wanted to see what folks think. In particular,
if you find the existing gating of updates for stable/branched releases
to cause problems in any way, I'd love to hear about it.
Thanks folks!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
10 months, 3 weeks
Fedora Workstation WG minutes, 2023-04-25
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2023-04-25)
==============================================
Meeting started by brainycmurf at 19:07:43 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-04-25/workstation...
.
Meeting summary
---------------
* Present members: Allan, Kalev, Chris, Owen (brainycmurf, 19:07:54)
* Guests: Luna Jernberg(bittin), jkonecny, mkolman (brainycmurf,
19:07:54)
* Regrets: Matthias, Tomas, Neal (brainycmurf, 19:07:54)
* Missing: (brainycmurf, 19:07:54)
* Secretary: Jens (brainycmurf, 19:07:54)
* FWWG Chair for Fedora 39 cycle (brainycmurf, 19:07:54)
* AGREED: Allan will be WG Chair for F39 cycle (brainycmurf,
19:07:58)
* Anaconda Web UI requirements (brainycmurf, 19:08:00)
* Replacement for custom partitioning (brainycmurf, 19:08:02)
* LINK: https://pagure.io/fedora-workstation/issue/375 (brainycmurf,
19:08:04)
* Separate home (brainycmurf, 19:08:51)
* LINK: https://pagure.io/fedora-workstation/issue/376 (brainycmurf,
19:08:53)
* Select partitioning scheme (brainycmurf, 19:09:04)
* LINK: https://pagure.io/fedora-workstation/issue/377 (brainycmurf,
19:09:06)
* Dual boot support (brainycmurf, 19:09:10)
* LINK: https://pagure.io/fedora-workstation/issue/371 (brainycmurf,
19:09:12)
* Announcements and status updates (brainycmurf, 19:09:16)
* LAS and HDR hackfest ongoing (brainycmurf, 19:09:20)
* Gnome 44.1 point releases (brainycmurf, 19:09:22)
* Last week's meeting minutes (brainycmurf, 19:09:24)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-04-19/workstation...
(brainycmurf, 19:09:26)
Meeting ended at 19:09:29 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (51)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year
Fedora Workstation WG minutes, 2023-04-18
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2023-04-18)
==============================================
Meeting started by brainycmurf at 23:47:57 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-04-19/workstation...
.
Meeting summary
---------------
* Present members: Kalev, Tomas, Owen, Jens, Allan, Chris, Michael, Neal
(brainycmurf, 23:48:09)
* Guests: Jiri, Martin (brainycmurf, 23:48:09)
* Regrets: Matthias (brainycmurf, 23:48:09)
* Missing: (brainycmurf, 23:48:09)
* Secretary: Kalev (brainycmurf, 23:48:09)
* Anaconda Web UI requirements (brainycmurf, 23:48:10)
* Ability to select a language and keyboard for installer and live
session: https://pagure.io/fedora-workstation/issue/366
(brainycmurf, 23:48:14)
* Ability to switch keyboard layouts during installation:
https://pagure.io/fedora-workstation/issue/368 (brainycmurf,
23:48:17)
* Anaconda Web UI requirements: Ability to reuse a /home partition or
subvolume: https://pagure.io/fedora-workstation/issue/367
(brainycmurf, 23:48:48)
* FWWG Chair for Fedora 39 cycle (brainycmurf, 23:49:16)
* Give ABRT some <3 (brainycmurf, 23:49:29)
* LINK: https://pagure.io/fedora-workstation/issue/130 (brainycmurf,
23:49:31)
* ACTION: Michael to discuss this with the ABRT team. (brainycmurf,
23:49:37)
* Announcements and status updates (brainycmurf, 23:49:44)
* New website! (brainycmurf, 23:49:46)
* Fedora 38 is released! (brainycmurf, 23:49:48)
* LAS is this week - https://linuxappsummit.org/ (brainycmurf,
23:49:50)
* HDR hackest next week -
https://wiki.gnome.org/Hackfests/ShellDisplayNext2023 (brainycmurf,
23:49:52)
Meeting ended at 23:49:54 UTC.
Action Items
------------
* Michael to discuss this with the ABRT team.
Action Items, by person
-----------------------
* Michael
* Michael to discuss this with the ABRT team.
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (47)
* zodbot (7)
* Michael (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year
Xorg issues on F38
by Michael Cronenworth
Hi,
I upgraded a few systems from F37 to F38 today and ran into some graphical glitches
on my Xorg/NVIDIA system that were not occurring on F37. Wayland systems do not have
the following issues.
* Thunderbird title bar does not react to mouse clicks to raise focus.[1]
* Same behavior seen in "mpv", VirtualBox, and a few other apps.
* Libreoffice has two major problems.
1. When not focused, the window is not "fully" drawn and other windows flicker
through it.
2. Mouse clicks are offset on the X and Y axis by about +50 pixels. Meaning
clicking a Calc cell results in the Cell above and to the left being clicked instead.
* Firefox or core Gnome applications do not have any graphical or behavior problems.
Any one else encountering this?
Thanks,
Michael
[1]
1 year
Fedora Workstation WG minutes, 2023-04-11
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2023-04-04)
==============================================
Meeting started by brainycmurf at 16:58:21 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-04-11/workstation...
.
Meeting summary
---------------
* Present members: Michael, Tomas, Allan, Chris, Matthias, Kalev, Jen
(brainycmurf, 16:58:35)
* Guests: (brainycmurf, 16:58:35)
* Regrets: Neal (brainycmurf, 16:58:35)
* Missing: Owen (brainycmurf, 16:58:35)
* Secretary: Chris (brainycmurf, 16:58:35)
* Fedora 38 final blockers (brainycmurf, 16:58:36)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/38/final/buglist
(brainycmurf, 16:58:38)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2176759
(brainycmurf, 16:58:45)
* No further action needed on our end. (brainycmurf, 16:58:47)
* Appoint chair for F39 release cycle (brainycmurf, 16:58:49)
* Any volunteers? Nomination period open. (brainycmurf, 16:58:51)
* append commands to bash history instead of overwriting (brainycmurf,
16:58:53)
* LINK: https://pagure.io/fedora-workstation/issue/364 (brainycmurf,
16:58:55)
* ACTION: Chris will write up a draft idea/proposal for devel@
discussion (brainycmurf, 16:58:57)
* Give ABRT some love (brainycmurf, 16:58:59)
* LINK: https://pagure.io/fedora-workstation/issue/130 (brainycmurf,
16:59:01)
* ABRT team needs help, issue has been open three years, priority
issues aren't getting fixed. (brainycmurf, 16:59:03)
* ACTION: Michael will followup (brainycmurf, 16:59:16)
* Announcements and status updates (brainycmurf, 16:59:18)
* There's a draft available of the what's new in F38 workstation
magazine article (brainycmurf, 16:59:20)
* LINK: https://pagure.io/fedora-magazine-newsroom/issue/173
(brainycmurf, 16:59:22)
* Last week's meeting minutes posted (brainycmurf, 16:59:27)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2023-04-05/workstation...
(brainycmurf, 16:59:29)
Meeting ended at 16:59:32 UTC.
Action Items
------------
* Chris will write up a draft idea/proposal for devel@ discussion
* Michael will followup
Action Items, by person
-----------------------
* Michael
* Michael will followup
* **UNASSIGNED**
* Chris will write up a draft idea/proposal for devel@ discussion
People Present (lines said)
---------------------------
* brainycmurf (33)
* zodbot (7)
* Michael (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year
