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, 2 weeks
Today's Workstation WG meeting is cancelled
by Allan Day
Hi all,
The Workstation WG was scheduled to have a meeting today, 29 November.
However, we have a few people out, and not much on the agenda, so I think
we should skip this one.
The next meeting should be 6 December.
Allan
1 year, 4 months
Fedora Workstation WG minutes, 2022-11-22
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2022-11-22)
==============================================
Meeting started by brainycmurf at 04:31:57 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-11-23/workstation...
.
Meeting summary
---------------
* Present members: Michael, Allan, Jens, Matthias, Owen, Tomas, Nate
(late), Neal (brainycmurf, 04:32:18)
* Guests: Zac (brainycmurf, 04:32:18)
* Regrets: Chris, Kalev (brainycmurf, 04:32:18)
* Missing: (brainycmurf, 04:32:18)
* Secretary: Tomáš (brainycmurf, 04:32:18)
* Cancel the last two meetings in the year 2022 (brainycmurf, 04:32:18)
* AGREED: (brainycmurf, 04:32:20)
* F38 change proposals (brainycmurf, 04:32:22)
* Deadline is 2022-12-27 (brainycmurf, 04:32:24)
* LINK: https://fedoraproject.org/wiki/Changes/UnfilteredFlathub
(brainycmurf, 04:32:40)
* ACTION: Check next week that the wiki pages were created.
(brainycmurf, 04:32:45)
* Should toolbox images block the release? (brainycmurf, 04:32:47)
* LINK: https://pagure.io/fedora-workstation/issue/337 (brainycmurf,
04:32:49)
* ACTION: Jens to talk to releng to see what their opinion is and then
to Fedora QA whether they could do some sanity checking
(brainycmurf, 04:32:56)
* Workstation user docs (brainycmurf, 04:32:59)
* LINK: https://pagure.io/fedora-workstation/pull-request/343
(brainycmurf, 04:33:01)
* ACTION: Allan to proceed with the PR and will coordinate with the
docs team. (brainycmurf, 04:33:09)
* Announcements, Status Updates (brainycmurf, 04:33:11)
* The minutes from last week have been posted. (brainycmurf,
04:33:13)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-11-15/workstation...
(brainycmurf, 04:33:15)
Meeting ended at 04:33:35 UTC.
Action Items
------------
* Check next week that the wiki pages were created.
* Jens to talk to releng to see what their opinion is and then to Fedora
QA whether they could do some sanity checking
* Allan to proceed with the PR and will coordinate with the docs team.
Action Items, by person
-----------------------
* Allan
* Allan to proceed with the PR and will coordinate with the docs team.
* **UNASSIGNED**
* Check next week that the wiki pages were created.
* Jens to talk to releng to see what their opinion is and then to
Fedora QA whether they could do some sanity checking
People Present (lines said)
---------------------------
* brainycmurf (34)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 5 months
Fedora Workstation WG minutes, 2022-11-15
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2022-11-15)
==============================================
Meeting started by brainycmurf at 22:08:25 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-11-15/workstation...
.
Meeting summary
---------------
* Present members: Michael, Allan, Kalev, Jens, Chris, Owen, Neal
(brainycmurf, 22:08:38)
* Guests: Luna(bittin) , Jimmac (brainycmurf, 22:08:38)
* Regrets: (brainycmurf, 22:08:38)
* Missing: (brainycmurf, 22:08:38)
* Secretary: Owen (brainycmurf, 22:08:38)
* F37 release status (brainycmurf, 22:08:39)
* Software changelogs should only use supported Markdown (brainycmurf,
22:08:46)
* LINK: https://pagure.io/fedora-workstation/issue/326 (brainycmurf,
22:08:48)
* ACTION: : Michael to file an Infra ticket (brainycmurf, 22:08:54)
* When skipping the option to enable 3rd repositories in the Fedora
post-installation experience, dl.flathub.org doesn't appear in GNOME
Software repo list, but all of the other 3rd repos do (brainycmurf,
22:08:56)
* LINK: https://pagure.io/fedora-workstation/issue/271 (brainycmurf,
22:08:59)
* ACTION: Owen will follow up on the ticket to describe what is going
on (brainycmurf, 22:09:03)
* Improve driver installation experience (brainycmurf, 22:09:05)
* LINK: https://pagure.io/fedora-workstation/issue/238 (brainycmurf,
22:09:07)
* ACTION: Owen to ask for who could come and talk about future
Nouveau/driver directions (brainycmurf, 22:09:17)
* Make VAAPI work out of the box (brainycmurf, 22:09:25)
* LINK: https://pagure.io/fedora-workstation/issue/209 (brainycmurf,
22:09:27)
* ACTION: Neal needs to follow-up on the package review for
intel-media-driver-free (brainycmurf, 22:09:31)
* Automatically install the OpenH264 codecs (brainycmurf, 22:09:35)
* LINK: https://pagure.io/fedora-workstation/issue/84 (brainycmurf,
22:09:37)
* Announcements, Status Updates (brainycmurf, 22:09:42)
* The minutes from last week have been posted. (brainycmurf,
22:09:56)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-11-09/workstation...
(brainycmurf, 22:09:58)
Meeting ended at 22:10:01 UTC.
Action Items
------------
* : Michael to file an Infra ticket
* Owen will follow up on the ticket to describe what is going on
* Owen to ask for who could come and talk about future Nouveau/driver
directions
* Neal needs to follow-up on the package review for
intel-media-driver-free
Action Items, by person
-----------------------
* **UNASSIGNED**
* : Michael to file an Infra ticket
* Owen will follow up on the ticket to describe what is going on
* Owen to ask for who could come and talk about future Nouveau/driver
directions
* Neal needs to follow-up on the package review for
intel-media-driver-free
People Present (lines said)
---------------------------
* brainycmurf (43)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 5 months
Fedora Workstation WG minutes, 2022-11-08
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2022-11-08)
==============================================
Meeting started by brainycmurf at 15:07:52 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-11-09/workstation...
.
Meeting summary
---------------
* Present members: Tom, Allan, Jens, Kalev, Chris, Michael,
(brainycmurf, 15:08:18)
* Guests: Zac (brainycmurf, 15:08:18)
* Regrets: Matthias (brainycmurf, 15:08:18)
* Missing: (brainycmurf, 15:08:18)
* Secretary: Chris (brainycmurf, 15:08:18)
* F37 release status (brainycmurf, 15:08:18)
* Working group chair for F38 (brainycmurf, 15:08:22)
* LINK: https://pagure.io/fedora-workstation/issue/338 (brainycmurf,
15:08:26)
* ACTION: We'll continue to discuss. (brainycmurf, 15:08:30)
* New tool needed for agendas and notes (brainycmurf, 15:08:32)
* LINK: https://pagure.io/fedora-workstation/issue/339 (brainycmurf,
15:08:34)
* ACTION: NO objections to using the openSUSE Etherpad instance
(brainycmurf, 15:08:41)
* Give ABRT some ❤ (brainycmurf, 15:08:43)
* LINK: https://pagure.io/fedora-workstation/issue/130 (brainycmurf,
15:08:45)
* copr packages for F37 ABRT to test (brainycmurf, 15:08:57)
* LINK:
https://copr.fedorainfracloud.org/coprs/g/abrt/abrt-debuginfod/
(brainycmurf, 15:08:59)
* Do we want to have Workstation User Documentation from F37 on up.
(brainycmurf, 15:09:01)
* LINK: https://pagure.io/fedora-workstation/issue/340 (brainycmurf,
15:09:03)
* GNOME Software format preference (brainycmurf, 15:09:28)
* Announcements, Status Updates (brainycmurf, 15:09:32)
* The minutes from last week have been posted. (brainycmurf,
15:09:34)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2022-11-02/workstation...
(brainycmurf, 15:09:36)
* ACTION: Chris to ask Ben if it's possible and useful to have release
notes put together sooner, to help with promotion (brainycmurf,
15:09:42)
Meeting ended at 15:09:47 UTC.
Action Items
------------
* We'll continue to discuss.
* NO objections to using the openSUSE Etherpad instance
* Chris to ask Ben if it's possible and useful to have release notes put
together sooner, to help with promotion
Action Items, by person
-----------------------
* **UNASSIGNED**
* We'll continue to discuss.
* NO objections to using the openSUSE Etherpad instance
* Chris to ask Ben if it's possible and useful to have release notes
put together sooner, to help with promotion
People Present (lines said)
---------------------------
* brainycmurf (44)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 5 months
