We might want to consider pushing out the branch point a week anyway to
help people get CTS in order?
On Fri, Jan 7, 2022 at 1:08 PM Ian Romanick wrote:
> Blarg. That all sounds awful. I think (hope!) I speak for everyone when
> I say that we all appreciate your and daniels' efforts to keep
The ac_surface_meta_address_test timeout occurs rarely and it's because the
test is computationally demanding. It's also possible the machine got
slower for some reason.
Marek
On Fri, Jan 7, 2022 at 12:32 PM Emma Anholt wrote:
> On Fri, Jan 7, 2022 at 6:18 AM Connor Abbott wrote:
> >
> >
On Fri, Jan 7, 2022 at 6:32 PM Emma Anholt wrote:
>
> On Fri, Jan 7, 2022 at 6:18 AM Connor Abbott wrote:
> >
> > Unfortunately batch mode has only made it *worse* - I'm sure it's not
> > intentional, but it seems that it's still running the CI pipelines
> > individually after the batch pipeline
Blarg. That all sounds awful. I think (hope!) I speak for everyone when
I say that we all appreciate your and daniels' efforts to keep this big
piece of machinery working.
If the problems persist much longer, should we consider pushing out the
22.0 branch point?
On 1/6/22 9:36 PM, Emma
On Fri, Jan 7, 2022 at 6:32 PM Emma Anholt wrote:
>
> On Fri, Jan 7, 2022 at 6:18 AM Connor Abbott wrote:
> >
> > Unfortunately batch mode has only made it *worse* - I'm sure it's not
> > intentional, but it seems that it's still running the CI pipelines
> > individually after the batch pipeline
On Fri, Jan 7, 2022 at 6:18 AM Connor Abbott wrote:
>
> Unfortunately batch mode has only made it *worse* - I'm sure it's not
> intentional, but it seems that it's still running the CI pipelines
> individually after the batch pipeline passes and not merging them
> right away, which completely
On Fri, Jan 7, 2022 at 3:18 PM Connor Abbott wrote:
>
> Unfortunately batch mode has only made it *worse* - I'm sure it's not
> intentional, but it seems that it's still running the CI pipelines
> individually after the batch pipeline passes and not merging them
> right away, which completely
Unfortunately batch mode has only made it *worse* - I'm sure it's not
intentional, but it seems that it's still running the CI pipelines
individually after the batch pipeline passes and not merging them
right away, which completely defeats the point. See, for example,
!14213 which has gone through
As you've probably noticed, there have been issues with git access
this week. The fd.o sysadmins are desperately trying to stay on
vacation because they do deserve a break, but have still been working
on the problem and a couple of solutions haven't worked out yet.
Hopefully we'll have some news
