Re: Thoughts welcome: interface between automated test gating and the "critical path"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2022-09-02 at 10:26 -0700, Adam Williamson wrote:
> 
> > > If we don't think it's worth doing that work, then we're kinda stuck
> > > with openQA glomming onto the critpath definition to decide which
> > > updates to test and gate, because I don't have any other current viable
> > > choices for that, really. And we'd have to figure out a critpath
> > > definition that's as viable as possible for both purposes.
> > > 
> > > 
> > > BTW, one other thought I've had in relation to all this is that we
> > > could enhance the current critpath definition somewhat. Right now, it's
> > > built out of package groups in comps which are kinda topic-separated:
> > > there's a critpath-kde, a critpath-gnome, a critpath-server, and so on.
> > > But the generated critical path package list is a monolith: it doesn't
> > > distinguish between a package that's on the GNOME critpath and a
> > > package that's on the KDE critpath, you just get a big list of all
> > > critpath packages. It might be nice if we actually did distinguish
> > > between those - the critpath definition could keep track of which
> > > critpath topic(s) a package is included in, and Bodhi could display
> > > that information in the web UI and provide it via the API. That way
> > > manual testers could get a bit more info on why a package is critpath
> > > and what areas to test, and openQA could potentially target its test
> > > runs to conserve resources a bit, though this might require a bit more
> > > coding work on the gating stuff now I think about it.
> > 
> > That sounds useful. We only need a volunteer to figure out the details
> > and do the work ;)
> 
> I actually did a huge rewrite of the thing that generates the critpath
> data this week, and it probably wouldn't be tooooo much work, honestly.
> The most annoying bit would be the Bodhi frontend stuff, but that's
> because I'm bad at frontend dev in general. :P But yeah, this is
> definitely off in sky-castle land. I'll add it to my ever-growing list
> of sky-castle projects to do when I get a couple of years of spare
> time...

So, an update on this whole area!

First off, I'm actually finding the time to do the sky-castle work. The
releng critpath script now outputs critpath data by group:
https://pagure.io/releng/c/621caa542acc142d57f1247e7644846f737f8eee?branch=main

Bodhi (git HEAD Bodhi, anyway) can now read data in that format:
https://github.com/fedora-infra/bodhi/pull/4755

and when this PR is merged, it will be able to mark updates as critpath
by groups:
https://github.com/fedora-infra/bodhi/pull/4759

This has the handy bonus effect of enabling us to remove one of our
remaining uses of PDC. Once the Bodhi work is merged, I can send a PR
for the releng ansible repo to define per-group greenwave policies, run
the critpath.py script nightly on the Bodhi boxes, and switch to the
'json' critpath type in Bodhi config, and finally I can then enhance
the openQA scheduler to only run the necessary tests for each update.

Second, since nobody really opposed the idea of extending the critpath
definition slightly, here's a formal proposal to implement that. I want
to edit the wiki critpath page:
https://fedoraproject.org/wiki/Critical_path_package

and change it as follows:

1. Under Background, change "The packages required to sustain these
actions make up the critical path." to:

"The packages required to sustain these actions initially made up the
critical path. Later, it was agreed that the maintainers of Editions,
spins, and labs can also declare packages that provide other key
functionality to be part of the ''critical path'' for that Edition,
spin or lab."

2. Under Actions, change the first two sentences to read:

"Packages required to perform the most fundamental actions on a system
are always considered part of the ''critical path''. Those actions
include: "

Does anyone object to these proposed changes? Thanks!
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux