From: Andrew Cooper <andrew.cooper3@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
<xen-devel@lists.xenproject.org>, Jan Beulich <jbeulich@suse.com>,
Ian Jackson <iwj@xenproject.org>
Subject: Re: [xen-unstable-smoke test] 159709: regressions - FAIL
Date: Fri, 26 Feb 2021 16:36:35 +0000 [thread overview]
Message-ID: <a33d2c9a-00e3-caf2-afa6-48f70ef1202c@citrix.com> (raw)
In-Reply-To: <osstest-159709-mainreport@xen.org>
On 26/02/2021 16:34, osstest service owner wrote:
> flight 159709 xen-unstable-smoke real [real]
> flight 159713 xen-unstable-smoke real-retest [real]
> http://logs.test-lab.xenproject.org/osstest/logs/159709/
> http://logs.test-lab.xenproject.org/osstest/logs/159713/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-qemuu-debianhvm-amd64 12 debian-hvm-install fail REGR. vs. 159704
Well - there's only one possibility here...
> commit 615367b5275a5b0123f1f1ee86c985fab234a5a4
> Author: Andrew Cooper <andrew.cooper3@citrix.com>
> Date: Thu Feb 25 16:54:17 2021 +0000
>
> x86/dmop: Properly fail for PV guests
>
> The current code has an early exit for PV guests, but it returns 0 having done
> nothing.
>
> Fixes: 524a98c2ac5 ("public / x86: introduce __HYPERCALL_dm_op...")
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Reviewed-by: Ian Jackson <iwj@xenproject.org>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> Release-Acked-by: Ian Jackson <iwj@xenproject.org>
which means we've something very wonky going on somewhere.
~Andrew
next prev parent reply other threads:[~2021-02-26 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 16:34 [xen-unstable-smoke test] 159709: regressions - FAIL osstest service owner
2021-02-26 16:36 ` Andrew Cooper [this message]
2021-02-26 16:44 ` 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=a33d2c9a-00e3-caf2-afa6-48f70ef1202c@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=iwj@xenproject.org \
--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 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).