On Thu, 2022-06-09 at 22:01 +0200, Miro HronĨok wrote:
On 09. 06. 22 21:48, Adam Williamson wrote:
> Hi folks!
>
> ...
>
> 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).
+1
> 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.
+1
> 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.
The delay happens only when we gate, or even when he tests results are
informational?
The delay would only happen with gating turned on.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net