Re: xen | Failed pipeline for staging | 511b9f28

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 25/05/2023 10:49 am, Jan Beulich wrote:
> On 24.05.2023 21:51, GitLab wrote:
>>
>> Pipeline #878023438 has failed!
>>
>> Project: xen ( https://gitlab.com/xen-project/xen )
>> Branch: staging ( https://gitlab.com/xen-project/xen/-/commits/staging )
>>
>> Commit: 511b9f28 ( 
>> https://gitlab.com/xen-project/xen/-/commit/511b9f286c3dadd041e0d90beeff7d47c9bf3b7a
>>  )
>> Commit Message: x86/spec-ctrl: Remove opencoded MSR_ARCH_CAPS c...
>> Commit Author: Andrew Cooper ( https://gitlab.com/andyhhp )
>>
>> Pipeline #878023438 ( 
>> https://gitlab.com/xen-project/xen/-/pipelines/878023438 ) triggered by 
>> Ganis ( https://gitlab.com/ganis )
>> had 3 failed jobs.
>>
>> Job #4345633611 ( https://gitlab.com/xen-project/xen/-/jobs/4345633611/raw )
>>
>> Stage: build
>> Name: opensuse-tumbleweed-gcc
>> Job #4345633612 ( https://gitlab.com/xen-project/xen/-/jobs/4345633612/raw )
>>
>> Stage: build
>> Name: opensuse-tumbleweed-gcc-debug
> While I understand these continue to be ignored failures,

It's a Qemu failure.  Olaf has a request out for a backport into the
qemu-xen tree.

>  I would have wanted
> to look at ...
>
>> Job #4345633615 ( https://gitlab.com/xen-project/xen/-/jobs/4345633615/raw )
>>
>> Stage: test
>> Name: build-each-commit-gcc
> ... the failure here. However, the log as shown ends at 4Mb as usual, yet not
> as usual the job artifacts consist of only config.log. So it's not clear
> whether anything relevant would want further looking into ...

This one is weird, and yes - there's nothing at all to go on.

First thing is to get the build log out reliably, because everything
else is guesswork.

This ended up failing on my pre-push run too, so I think it's something
deterministic on larger pushes, but I'm positive that my series is fully
bisectable, so I suspect it's not a content issue.

~Andrew