[PATCH] Azure/GitLab: Use buildman -T0 for binman, etc, test
Simon Glass
sjg at chromium.org
Fri Mar 5 05:09:26 CET 2021
Hi Tom, Bin,
On Thu, 4 Mar 2021 at 22:51, Tom Rini <trini at konsulko.com> wrote:
>
> On Fri, Mar 05, 2021 at 10:05:16AM +0800, Bin Meng wrote:
> > Hi Tom,
> >
> > On Fri, Mar 5, 2021 at 6:04 AM Tom Rini <trini at konsulko.com> wrote:
> > >
> > > There are times where buildman seems to get stuck in this job when in
> > > CI. Forcing single-threaded here allows us to complete and move on.
> >
> > Is this a potential buildman bug? +Simon
>
> Kinda? Simon and I were talking about it on IRC, and taking this was
> his suggestion.
>
> > My concern is this will increase the overall CI time
>
> It shouldn't, since we only build a single board here. Further, it
> fixes or papers over CI failures where the job gets stuck.
Yes it should not affect performance.
It is a bit sad though. I think 'papers over' is accurate. I was
actually expecting to get a Python error and then be able to debug it.
I was not expecting that the bug would just go away.
I have not been able to repeat the problem locally. It is as if
buildman hangs somewhere in the builder thread and/or the output never
makes it back up to the main thread.
Regards,
Simon
More information about the U-Boot
mailing list