On Mon, Jan 24, 2022 at 09:15:42PM +0100, Dan Horák wrote:
> > Perhaps we could merge today and then do another pass of failed builds
> > into f36-rebuild tag and merge that back on thursday or something?
> > Can we easily identify those builds that failed due to these ppc64le
> > issues?
>
> it s
On Mon, 24 Jan 2022 12:10:37 -0800
Kevin Fenzi wrote:
> On Mon, Jan 24, 2022 at 08:08:25PM +0100, Jakub Jelinek wrote:
> > On Mon, Jan 24, 2022 at 08:00:31PM +0100, Vitaly Zaitsev via devel wrote:
> > > On 24/01/2022 19:06, Kevin Fenzi wrote:
> > > > This seems kind of high, so we are going t
On Mon, Jan 24, 2022 at 08:08:25PM +0100, Jakub Jelinek wrote:
> On Mon, Jan 24, 2022 at 08:00:31PM +0100, Vitaly Zaitsev via devel wrote:
> > On 24/01/2022 19:06, Kevin Fenzi wrote:
> > > This seems kind of high, so we are going to resubmit all the failed
> > > builds in a short second round to re
On Mon, Jan 24, 2022 at 08:00:31PM +0100, Vitaly Zaitsev via devel wrote:
> On 24/01/2022 19:06, Kevin Fenzi wrote:
> > This seems kind of high, so we are going to resubmit all the failed
> > builds in a short second round to reduce the chance of transitory issues
> > causing the build failures.
>
On 24/01/2022 19:06, Kevin Fenzi wrote:
This seems kind of high, so we are going to resubmit all the failed
builds in a short second round to reduce the chance of transitory issues
causing the build failures.
I think the ppc64 GCC regressions should be fixed first.
--
Sincerely,
Vitaly Zaits
The mass rebuild finished early saturday morning.
This resulted in 3448 failed builds.
This seems kind of high, so we are going to resubmit all the failed
builds in a short second round to reduce the chance of transitory issues
causing the build failures.
It's expected that should finish later
