From: Jan Beulich <jbeulich@suse.com>
To: Ian Jackson <iwj@xenproject.org>,
Anthony Perard <anthony.perard@citrix.com>
Cc: xen-devel@lists.xenproject.org,
osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [xen-unstable test] 162845: regressions - FAIL
Date: Wed, 16 Jun 2021 09:12:52 +0200 [thread overview]
Message-ID: <8e39ca8f-3202-7d3a-d65d-7087634bd49e@suse.com> (raw)
In-Reply-To: <osstest-162845-mainreport@xen.org>
On 16.06.2021 08:54, osstest service owner wrote:
> flight 162845 xen-unstable real [real]
> flight 162853 xen-unstable real-retest [real]
> http://logs.test-lab.xenproject.org/osstest/logs/162845/
> http://logs.test-lab.xenproject.org/osstest/logs/162853/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemuu-ovmf-amd64 15 guest-saverestore fail REGR. vs. 162533
> test-amd64-i386-xl-qemuu-ovmf-amd64 15 guest-saverestore fail REGR. vs. 162533
There looks to still be an issue with the ovmf version used. I'm
puzzled to find this flight reporting
built_revision_ovmf e1999b264f1f9d7230edf2448f757c73da567832
which isn't what the tree recently was rewound to, but about two
dozen commits older. I hope one of you has a clue at what is going
on here.
Jan
next prev parent reply other threads:[~2021-06-16 7:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 6:54 [xen-unstable test] 162845: regressions - FAIL osstest service owner
2021-06-16 7:12 ` Jan Beulich [this message]
2021-06-16 14:21 ` Anthony PERARD
2021-06-16 14:49 ` Jan Beulich
2021-06-16 15:01 ` Jan Beulich
2021-06-16 15:12 ` Anthony PERARD
2021-06-16 15: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=8e39ca8f-3202-7d3a-d65d-7087634bd49e@suse.com \
--to=jbeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=iwj@xenproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).