From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
osstest service owner <osstest-admin@xenproject.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [xen-4.8-testing test] 114505: regressions - FAIL
Date: Mon, 16 Oct 2017 17:51:37 +0100 [thread overview]
Message-ID: <c6b1e8ab-8b5b-3a68-26d9-02bcf97e429e@citrix.com> (raw)
In-Reply-To: <23012.52536.721870.990032@mariner.uk.xensource.com>
On 16/10/17 16:16, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [Xen-devel] [xen-4.8-testing test] 114505: regressions - FAIL"):
>> On 15/10/17 20:45, osstest service owner wrote:
>>> flight 114505 xen-4.8-testing real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/114505/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>> test-xtf-amd64-amd64-2 48 xtf/test-hvm64-lbr-tsx-vmentry fail REGR. vs. 114173
> ...
>> Ian: These tests exercise something very machine specific, and the XTF
>> tests really do need tying to specific hardware when making regression
>> considerations.
> Is this test new enough that it might have never run on that
> hardware ? If so then a force push might be justified.
andrewcoop@andrewcoop:/local/xen-test-framework.git$ git show --format=fuller 36d926fe
commit 36d926fe0e9b7db39965f430cdb4c5f1daf4eef3
Author: Andrew Cooper <andrew.cooper3@citrix.com>
AuthorDate: Wed Oct 12 18:23:42 2016
Commit: Andrew Cooper <andrew.cooper3@citrix.com>
CommitDate: Tue Apr 25 13:55:42 2017
LBR/TSX VMentry failure test
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
It has been running in OSSTest for a fair while now.
The test will only fail on versions of Xen before the fixes went in
(Currently Xen 4.9), on Haswell and Broadwell hardware.
Its also possible
> It is difficult to tie the tests to specific hardware without
> insisting that every run uses every host.
How hard would it be to tag each flight with which host it ran on, and
filter for host == current when determining whether a regression has
occurred?
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-16 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 19:45 [xen-4.8-testing test] 114505: regressions - FAIL osstest service owner
2017-10-16 9:14 ` Andrew Cooper
2017-10-16 15:16 ` Ian Jackson
2017-10-16 16:51 ` Andrew Cooper [this message]
2017-10-16 16:12 ` Jan Beulich
2017-10-16 16:38 ` Andrew Cooper
2017-10-17 6:17 ` 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=c6b1e8ab-8b5b-3a68-26d9-02bcf97e429e@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.jackson@eu.citrix.com \
--cc=osstest-admin@xenproject.org \
--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).