From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
osstest-admin@xenproject.org
Subject: Re: [xen-4.6-testing test] 107186: regressions - trouble: broken/fail/pass
Date: Wed, 5 Apr 2017 14:11:36 +0100 [thread overview]
Message-ID: <f1511141-4ff8-39cd-3e07-6c4ef173f617@citrix.com> (raw)
In-Reply-To: <58E4D151020000780014D14B@prv-mh.provo.novell.com>
On 05/04/17 10:13, Jan Beulich wrote:
>>>> On 05.04.17 at 06:27, <osstest-admin@xenproject.org> wrote:
>> flight 107186 xen-4.6-testing real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/107186/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-amd64-i386-freebsd10-amd64 3 host-install(3) broken REGR. vs. 107151
>> test-xtf-amd64-amd64-5 20 xtf/test-hvm32-invlpg~shadow fail REGR. vs. 107151
>> test-xtf-amd64-amd64-5 33 xtf/test-hvm32pae-invlpg~shadow fail REGR. vs. 107151
>> test-xtf-amd64-amd64-5 44 xtf/test-hvm64-invlpg~shadow fail REGR. vs. 107151
> Are these tests CPU vendor dependent in some way? The
> previous pass was on an Intel box, the failures here are on an
> AMD one.
This is because the XTF tests aren't locked to specific hardware. I
pointed this problem out when the 5-way split was being considered.
These failures are wont-fix on AMD hardware on Xen 4.6, due to the
invasiveness of the backports, but having the different flights
scheduled across hardware will cause false negatives as shown here.
This is an OSS test bug, not a Xen bug.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-04-05 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 4:27 [xen-4.6-testing test] 107186: regressions - trouble: broken/fail/pass osstest service owner
2017-04-05 9:13 ` Jan Beulich
2017-04-05 13:11 ` 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=f1511141-4ff8-39cd-3e07-6c4ef173f617@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.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 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).