From: Jan Beulich <jbeulich@suse.com>
To: Ian Jackson <iwj@xenproject.org>
Cc: xen-devel@lists.xenproject.org,
osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [xen-unstable bisection] complete test-xtf-amd64-amd64-4
Date: Fri, 11 Jun 2021 08:41:32 +0200 [thread overview]
Message-ID: <1fb151ef-e04a-f244-6c2a-5b562893a2a9@suse.com> (raw)
In-Reply-To: <E1lrWnM-0003Ul-QG@osstest.test-lab.xenproject.org>
Ian,
On 11.06.2021 04:21, osstest service owner wrote:
> branch xen-unstable
> xenbranch xen-unstable
> job test-xtf-amd64-amd64-4
> testid xtf/test-pv32pae-selftest
>
> Tree: linux git://xenbits.xen.org/linux-pvops.git
> Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
> Tree: qemuu git://xenbits.xen.org/qemu-xen.git
> Tree: xen git://xenbits.xen.org/xen.git
> Tree: xtf git://xenbits.xen.org/xtf.git
>
> *** Found and reproduced problem changeset ***
>
> Bug is in tree: xen git://xenbits.xen.org/xen.git
> Bug introduced: 1a0f2fe2297d122a08fee2b26de5de995fdeca13
> Bug not present: 5268b2dcf7e5342c8a51ceb4bed3e7740c69f5c1
> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/162627/
>
>
> commit 1a0f2fe2297d122a08fee2b26de5de995fdeca13
> Author: George Dunlap <george.dunlap@citrix.com>
> Date: Thu May 6 13:38:02 2021 +0100
>
> SUPPORT.md: Un-shimmed 32-bit PV guests are no longer supported
>
> The support status of 32-bit guests doesn't seem particularly useful.
>
> With it changed to fully unsupported outside of PV-shim, adjust the PV32
> Kconfig default accordingly.
>
> Reported-by: Jann Horn <jannh@google.com>
> Signed-off-by: George Dunlap <george.dunlap@citrix.com>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
as indicated upfront, and as now also confirmed by the large amount of
failures in the two most recent full unstable flights, our defaulting
to off of PV32 for non-shim Xen builds means in osstest PV32 needs to
be turned on again, or all the 32-bit PV Dom0 / DomU tests (and xtf
equivalents) would need to be disabled. This will eventually be needed
on all branches which we would backport this change to (I expect this
would be at least all fully maintained ones), and which have a PV32
setting (exists only as of 4.14).
As I don't expect disabling any tests is a reasonable course of action,
I think it's going to need to be the .config override. Could you please
arrange for this?
Jan
next prev parent reply other threads:[~2021-06-11 6:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 2:21 [xen-unstable bisection] complete test-xtf-amd64-amd64-4 osstest service owner
2021-06-11 6:41 ` Jan Beulich [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-13 17:21 osstest service owner
2021-02-25 23:27 osstest service owner
2020-09-28 3:35 osstest service owner
2020-09-25 20:52 osstest service owner
2018-10-13 20:58 osstest service owner
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=1fb151ef-e04a-f244-6c2a-5b562893a2a9@suse.com \
--to=jbeulich@suse.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).