Hi
On Tue, Jul 12, 2022 at 10:10 AM Richard Henderson
<richard.henderson@linaro.org> wrote:
>
> On 7/12/22 09:24, Richard Henderson wrote:
> > On 7/11/22 13:26, marcandre.lureau@redhat.com wrote:
> >> From: Marc-André Lureau <marcandre.lureau@redhat.com>
> >>
> >> Hi
> >>
> >> This is a small series to attempt to debug "Intermittent meson failures on
> >> msys2" and improve a bit msys2/gitlab reports.
> >
> > Thanks. I've pushed this to staging for a test run:
> >
> > https://gitlab.com/qemu-project/qemu/-/pipelines/585473909
>
> Amusingly, both msys2 jobs passed the first time, but I reran and now have a failure for
> your investigation:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/2707801937
>
Hmm, there are no artifacts. How come? meson-logs/ should be there..
Anyway, I am not sure it would have more details about the failing
command.
Sadly we don't have any stderr output, and ninja doesn't log the
failing command exit code either. I guess I will try with a custom
ninja build now.
I think I have triggered 10x times the build now, but I am not reaching the build error, only random build time over 1h10 limit...