From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>, xen-devel@lists.xenproject.org
Cc: osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [xen-unstable test] 184940: regressions - FAIL
Date: Fri, 8 Mar 2024 13:59:25 +0000 [thread overview]
Message-ID: <b9ecffeb-cbef-4be7-bb85-224cbc11a35b@citrix.com> (raw)
In-Reply-To: <5c21d349-5021-490f-bc6b-eb5973622688@suse.com>
On 08/03/2024 1:56 pm, Jan Beulich wrote:
> On 08.03.2024 14:45, osstest service owner wrote:
>> flight 184940 xen-unstable real [real]
>> flight 184945 xen-unstable real-retest [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/184940/
>> http://logs.test-lab.xenproject.org/osstest/logs/184945/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-amd64-amd64-livepatch 13 livepatch-run fail REGR. vs. 184927
>> test-amd64-i386-livepatch 13 livepatch-run fail REGR. vs. 184927
> Hmm, both have "(XEN) common/livep" following the shell prompt,
> i.e. an incomplete hypervisor log message (maybe a failed assertion?),
> suggesting a triple fault may have occurred. While some livepatch
> related changes are under test, I can't (for now) connect any of them
> (or any of the other changes) with such behavior.
Well... that's ominously my changes then, but our testing seems happy
with them.
~Andrew
prev parent reply other threads:[~2024-03-08 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 13:45 [xen-unstable test] 184940: regressions - FAIL osstest service owner
2024-03-08 13:56 ` Jan Beulich
2024-03-08 13:59 ` Andrew Cooper [this message]
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=b9ecffeb-cbef-4be7-bb85-224cbc11a35b@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--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.