On Tue, 2022-10-18 at 09:37 -0400, pmkel...@frontier.com wrote:
> >
> > 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:
> >
On 10/17/22 8:45 PM, Adam Williamson wrote:
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
On Mon, Oct 17, 2022 at 8:54 PM Adam Williamson
wrote:
>
> Does anyone object to these proposed changes? Thanks!
Ship it!
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list --
On Tue, Oct 18, 2022 at 02:45:32AM +0200, Adam Williamson wrote:
> 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
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
> > >
On Fri, 2022-09-02 at 08:37 +, Zbigniew Jędrzejewski-Szmek wrote:
> >
> > Now, because I glued openQA to the critpath because it was handy, there
> > are two sets of consequences to a package being in critical path:
> >
> > 1. Tighter Bodhi requirements
> > 2. openQA tests are run, and
I have a naive question...
I wonder if the folks who do a lot of zuul-ci (eg. opendev.org or
https://www.softwarefactory-project.io ) have methods to determine which
gating criteria to automate?
-Blaise
On Fri, Sep 2, 2022 at 10:39 AM Kalev Lember wrote:
> On Fri, Sep 2, 2022 at 3:16 PM Ben
On Fri, Sep 2, 2022 at 3:16 PM Ben Cotton wrote:
> On Wed, Aug 31, 2022 at 12:00 PM Adam Williamson
> wrote:
>
> > So, one of the implicit questions here is, is it OK to keep twinning
> > these two sets of consequences, or should we split them up?
>
> Yes, it's okay to keep two sets of
On Wed, Aug 31, 2022 at 12:00 PM Adam Williamson
wrote:
> So, one of the implicit questions here is, is it OK to keep twinning
> these two sets of consequences, or should we split them up?
Yes, it's okay to keep two sets of consequences together. In fact,
it's preferable. One critpath to rule
On Wed, Aug 31, 2022 at 08:59:49AM -0700, Adam Williamson wrote:
> On Wed, 2022-08-31 at 12:43 +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Tue, Aug 30, 2022 at 12:10:00PM -0700, Adam Williamson wrote:
> > > On Tue, 2022-08-30 at 09:14 -0400, Ben Cotton wrote:
> > > > From my perspective,
On Wed, 2022-08-31 at 12:43 +, Zbigniew Jędrzejewski-Szmek wrote:
> On Tue, Aug 30, 2022 at 12:10:00PM -0700, Adam Williamson wrote:
> > On Tue, 2022-08-30 at 09:14 -0400, Ben Cotton wrote:
> > > From my perspective, anything that blocks the release is on the
> > > critical path. So any time
On Tue, Aug 30, 2022 at 12:10:00PM -0700, Adam Williamson wrote:
> On Tue, 2022-08-30 at 09:14 -0400, Ben Cotton wrote:
> > From my perspective, anything that blocks the release is on the
> > critical path. So any time there's a violation of the release criteria
> > and the package is not on the
On ti, 30 elo 2022, Adam Williamson wrote:
On Tue, 2022-08-30 at 09:39 +0300, Alexander Bokovoy wrote:
On ma, 29 elo 2022, Adam Williamson wrote:
> On Tue, 2022-08-30 at 00:32 -0400, DJ Delorie wrote:
> > It sounds to me like the problem is "how do we best use the available
> > automated test
On Tue, 2022-08-30 at 09:14 -0400, Ben Cotton wrote:
> From my perspective, anything that blocks the release is on the
> critical path. So any time there's a violation of the release criteria
> and the package is not on the critical path definition, that's a bug
> in the definition.
>
> I
On Tue, 2022-08-30 at 10:19 +0200, Petr Pisar wrote:
> V Tue, Aug 30, 2022 at 09:39:27AM +0300, Alexander Bokovoy napsal(a):
> > On ma, 29 elo 2022, Adam Williamson wrote:
> > > On Tue, 2022-08-30 at 00:32 -0400, DJ Delorie wrote:
> > > > It sounds to me like the problem is "how do we best use the
On Tue, 2022-08-30 at 09:39 +0300, Alexander Bokovoy wrote:
> On ma, 29 elo 2022, Adam Williamson wrote:
> > On Tue, 2022-08-30 at 00:32 -0400, DJ Delorie wrote:
> > > It sounds to me like the problem is "how do we best use the available
> > > automated test resources?" so I'll answer accordingly.
From my perspective, anything that blocks the release is on the
critical path. So any time there's a violation of the release criteria
and the package is not on the critical path definition, that's a bug
in the definition.
I recognize that this is a somewhat naïve view. For one, it may
broaden
V Tue, Aug 30, 2022 at 09:39:27AM +0300, Alexander Bokovoy napsal(a):
> On ma, 29 elo 2022, Adam Williamson wrote:
> > On Tue, 2022-08-30 at 00:32 -0400, DJ Delorie wrote:
> > > It sounds to me like the problem is "how do we best use the available
> > > automated test resources?" so I'll answer
On ma, 29 elo 2022, Adam Williamson wrote:
On Tue, 2022-08-30 at 00:32 -0400, DJ Delorie wrote:
It sounds to me like the problem is "how do we best use the available
automated test resources?" so I'll answer accordingly. Ignore me if I
misunderstood ;-)
No, not really, sorry if I didn't
On Tue, 2022-08-30 at 00:32 -0400, DJ Delorie wrote:
> It sounds to me like the problem is "how do we best use the available
> automated test resources?" so I'll answer accordingly. Ignore me if I
> misunderstood ;-)
No, not really, sorry if I didn't explain clearly enough :D It's more
just a
It sounds to me like the problem is "how do we best use the available
automated test resources?" so I'll answer accordingly. Ignore me if I
misunderstood ;-)
We currently have a small list of packages that are gated behind openQA,
and insufficient openQA resources to expand this list to all
On Mon, Aug 29, 2022 at 03:50:02PM -0700, Adam Williamson wrote:
...snip...
>
> I can think of I guess four options:
>
> 1. Broaden the definition of the "critical path" somehow. We could just
> write in that it includes FreeIPA functionality, I guess, though that
> seems special purpose. We
22 matches
Mail list logo
