From: Jan Beulich <jbeulich@suse.com>
To: Henry Wang <Henry.Wang@arm.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"osstest service owner" <osstest-admin@xenproject.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [xen-unstable test] 174896: regressions - trouble: broken/fail/pass
Date: Tue, 22 Nov 2022 08:27:06 +0100 [thread overview]
Message-ID: <44dfd2eb-9ef8-7254-70a1-e41177d6c9af@suse.com> (raw)
In-Reply-To: <AS8PR08MB79912EE5EF2BA9A0F9527416920D9@AS8PR08MB7991.eurprd08.prod.outlook.com>
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.
Jan
> [1] http://logs.test-lab.xenproject.org/osstest/logs/174896/test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm/sabro1---var-log-xen-osstest-serial-debianhvm.guest.osstest.log
>
> [2] http://logs.test-lab.xenproject.org/osstest/logs/174896/test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm/serial-sabro1.log.0
>
> [3] http://logs.test-lab.xenproject.org/osstest/logs/174896/test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm/serial-sabro1.log
>
> Kind regards,
> Henry
next prev parent reply other threads:[~2022-11-22 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 4:17 [xen-unstable test] 174896: regressions - trouble: broken/fail/pass osstest service owner
2022-11-22 4:40 ` Henry Wang
2022-11-22 7:27 ` Jan Beulich [this message]
2022-11-22 7:30 ` Henry Wang
2022-11-22 7:34 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44dfd2eb-9ef8-7254-70a1-e41177d6c9af@suse.com \
--to=jbeulich@suse.com \
--cc=Henry.Wang@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=osstest-admin@xenproject.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.