From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
osstest service owner <osstest-admin@xenproject.org>
Cc: xen-devel@lists.xensource.com,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [xen-unstable test] 94672: regressions - trouble: blocked/broken/fail/pass
Date: Sun, 22 May 2016 16:03:47 +0100 [thread overview]
Message-ID: <5741CA53.60000@citrix.com> (raw)
In-Reply-To: <20160522145832.GA13041@citrix.com>
On 22/05/16 15:58, Wei Liu wrote:
> On Sun, May 22, 2016 at 09:14:36AM +0000, osstest service owner wrote:
>> flight 94672 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/94672/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR. vs. 94580
> This has been consistently failing in the last 5 flights.
>
> The most likely culprit seems to be
>
> x86emul: suppress writeback upon unsuccessful MMX/SSE/AVX insn emulation
The bisector (message
<E1b4M5H-0007yh-V5@osstest.test-lab.xenproject.org> ) fingers your bump
of the ovmf version, which precedes this MMX change.
However, it is curious as your bump of the ovmf has already passed the
push gate.
Either the bisector is right, in which case why did your ovmf change get
into master in the first place, or the bisector is wrong, in which case
why didn't it identify this change as the culprit. I am confused.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-22 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 9:14 [xen-unstable test] 94672: regressions - trouble: blocked/broken/fail/pass osstest service owner
2016-05-22 14:58 ` Wei Liu
2016-05-22 15:03 ` Andrew Cooper [this message]
2016-05-22 15:39 ` Wei Liu
2016-05-23 8: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=5741CA53.60000@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=osstest-admin@xenproject.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).