Re: [Xen-devel] [xen-4.8-testing test] 114505: regressions - FAIL

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

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@xxxxxxxxxx>
AuthorDate: Wed Oct 12 18:23:42 2016
Commit:     Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
CommitDate: Tue Apr 25 13:55:42 2017

    LBR/TSX VMentry failure test
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

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@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel