Re: [xen-unstable test] 174896: regressions - trouble: broken/fail/pass

[Jan Beulich <jbeulich@xxxxxxxx>]

On 22.11.2022 08:30, Henry Wang wrote:
> Hi Jan,
> 
>> -----Original Message-----
>> From: Jan Beulich <jbeulich@xxxxxxxx>
>> Subject: Re: [xen-unstable test] 174896: regressions - trouble:
>> broken/fail/pass
>>
>> On 22.11.2022 05:40, Henry Wang wrote:
>>> Hi,
>>>
>>>> -----Original Message-----
>>>> Subject: [xen-unstable test] 174896: regressions - trouble:
>> broken/fail/pass
>>>>
>>>> flight 174896 xen-unstable real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/174896/
>>>>
>>>> Regressions :-(
>>>>
>>>> Tests which did not succeed and are blocking,
>>>> including tests which could not be run:
>>>>  test-amd64-i386-xl-qemut-debianhvm-amd64    <job status>
>> broken
>>>>  test-amd64-i386-xl-qemut-debianhvm-amd64 5 host-install(5) broken
>> REGR.
>>>> vs. 174797
>>>>  test-amd64-amd64-examine-bios  5 host-install          broken REGR. vs.
>>>> 174797
>>>>  test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm 12 debian-hvm-install
>>>> fail REGR. vs. 174797
>>>
>>> Seeing [1] [2] and [3], I guess there is still something wrong or it is 
>>> just an
>> OSSTest glitch?
>>
>> The first three are certainly osstest / environment issues, which is
>> generally the case when a test's status is "broken". The 4th, as
>> already said in reply to flight 172089, is a test which sadly fails
>> every now and then. So let's hope for another flight and better luck.
> 
> Thanks for the confirmation, this is reassuring and I guess I am getting too
> sensitive now :) Sorry I somehow missed your reply to 172089, next time I
> will check my inbox history first.

Oh, I'm sorry, no, this was not a complaint in any way. It was merely
an attempt to make people look at the state just in case they can see
a way to analyze the cause of these random failures; I for one still
have no good idea.

Jan