<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 12, 2022 at 10:22 AM Leon Fauster via CentOS-devel <<a href="mailto:centos-devel@centos.org">centos-devel@centos.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Am 12.09.22 um 16:47 schrieb Troy Dawson:<br>
> <br>
> <br>
> On Sun, Sep 11, 2022 at 2:05 AM Phil Perry <<a href="mailto:pperry@elrepo.org" target="_blank">pperry@elrepo.org</a> <br>
> <mailto:<a href="mailto:pperry@elrepo.org" target="_blank">pperry@elrepo.org</a>>> wrote:<br>
> <br>
> On 11/09/2022 08:41, Branislav Náter wrote:<br>
> > Hi,<br>
> ><br>
> ><br>
> > On Sat, Sep 10, 2022 at 8:46 PM Leon Fauster via CentOS-devel<br>
> > <<a href="mailto:centos-devel@centos.org" target="_blank">centos-devel@centos.org</a> <mailto:<a href="mailto:centos-devel@centos.org" target="_blank">centos-devel@centos.org</a>><br>
> <mailto:<a href="mailto:centos-devel@centos.org" target="_blank">centos-devel@centos.org</a> <mailto:<a href="mailto:centos-devel@centos.org" target="_blank">centos-devel@centos.org</a>>>><br>
> wrote:<br>
> ><br>
> > I wonder about the current firefox build 91.13.0-1.el9? Its<br>
> not on the<br>
> > mirrors (comp 20220829) nor in the last prod compose<br>
> (20220909) / both<br>
> > lists firefox-91.11.0-2.el9 ... Thanks.<br>
> ><br>
> ><br>
> > For inclusion in the compose, it has to pass testing. Testing is<br>
> still<br>
> > in progress.<br>
> ><br>
> ><br>
> <br>
> I'm just trying to understand how it can still be in testing for Stream<br>
> when it has clearly passed testing and been released to RHEL? I thought<br>
> Stream sat 'upstream' of RHEL?<br>
> <br>
> What extra testing is performed for packages in Stream that is not<br>
> performed for the same packages in RHEL? What tests are failing? Should<br>
> we be concerned as RHEL users that we are not receiving the full<br>
> testing<br>
> experience?<br>
> <br>
> <br>
> So people know the sequence of events.<br>
> <br>
> firefox-91.13.0-1.el9_0 was built in RHEL 9.0 on 2022-08-18<br>
> - The build passed all of it's gating tests.<br>
> - This was built on a RHEL 9.0 buildroot, and tested on a RHEL 9.0 buildroot<br>
> - This got pushed to RHEL 9.0 only<br>
> <br>
> firefox-91.13.0-1.el9 was built on CentOS Stream 9 and RHEL 9.1 on <br>
> 2022-08-25<br>
> - This build did not pass it's gating tests - it still hasn't<br>
> - This was built on a RHEL 9.1 buildroot, and tested on a RHEL 9.1 buildroot<br>
> - As far as I can tell, it's got the same tests. It's possible that one <br>
> or more of the tests went from "warn when it fails" to "fail when it <br>
> fails", but it looks like the tests are the same.<br>
> - It's also possible that something changed in RHEL 9.1 that is causing <br>
> the tests to fail.<br>
> - I'm not on the firefox team, I'm just looking at the gating system, <br>
> and to be honest, when I look beyond the "passed" - "failed" parts and <br>
> into the results, I get lost.<br>
> <br>
> From everything I can see, this delay wasn't the result of an embargo, <br>
> simply tests not passing.<br>
> <br>
<br>
<br>
I had the understanding that those gates are responsible to sync between <br>
RHEL/CENTOS build pipelines? Especially for the major version 9 this <br>
should be the state or do I misunderstand the workflow?<br>
<br>
--<br>
Leon<br></blockquote><div><br></div><div>Since I don't exactly know what you are picturing as a workflow, I'll step through an average package update on RHEL9. <br></div><div><br></div>1 - maintainer (or others) create a merge request into CentOS Stream 9 gitlab area.<div>2 - the merge request is gated and tested before being merged.<br></div><div>3 - When that merge request gets merged in the Stream 9 gitlab area, it is also synced over to the internal Brew dist-git area.</div><div>4 - The maintainer starts the build in CentOS Stream 9.</div><div>5 - When that happens, a build starts on the internal Brew systems.</div><div>6 - When both builds finish, they are both gated. The testing only happens internally on the Brew build.</div><div>7 - When the internal testing passes successfully, then both RHEL and CS builds are moved on.</div><div>8 - Internally, an errata is made, or an errata is updated with the new build, and both packages move to -pending.</div><div>9 - Composes are created out of the -pending packages.</div><div><br></div><div>Early on there was talk about putting gating between CS and RHEL, but that would make the build repo's different, and eventually the CentOS Stream and RHEL builds would diverge.</div></div><div class="gmail_quote"><br></div><div class="gmail_quote">I've simplified the steps some, and it's possible I didn't explain everything correctly. So if you need me (or others) to explain or expand on some of the steps, let me know.</div><div class="gmail_quote"><br></div><div class="gmail_quote">Troy</div><div class="gmail_quote"><br></div></div>