Re: [Xen-devel] [xen-unstable test] 115037: regressions - FAIL

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 23/10/17 15:34, Jan Beulich wrote:
>>>> On 23.10.17 at 15:58, <julien.grall@xxxxxxxxxx> wrote:
>> On 23/10/17 09:40, Jan Beulich wrote:
>>>>>> On 23.10.17 at 01:49, <osstest-admin@xxxxxxxxxxxxxx> wrote:
>>>> flight 115037 xen-unstable real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/115037/ 
>>>>
>>>> Regressions :-(
>>>>
>>>> Tests which did not succeed and are blocking,
>>>> including tests which could not be run:
>>>>   test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop        fail REGR. vs. 
>>>> 114644
>>>>   test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop       fail REGR. vs. 
>>>> 114644
>>>>   test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop       fail REGR. vs. 
>>>> 114644
>>> I'm puzzled by these recurring failures: Until flight 114525 all three
>>> (plus the fourth sibling, which is in "guest-stop fail never pass" state)
>>> were fail-never-pass on windows-install (the 64-bit host ones) or
>>> guest-saverestore (the 32-bit host ones). Then flights 114540 and
>>> 114644 were successes, and since then guest-stop has been failing.
>>> The guest console doesn't show any indication that the guest may
>>> have received a shutdown signal.
>> Would it be possible of a platform specific bug? The last two flights 
>> are failing on merlot1.
> Not very likely here, I would say.

These tests have reliably never passed before, and there are no changes
recently (I'm aware of) which would cause them to start passing.

The windows VMs aren't running PV drivers, so have no clue about the
xenstore control key, or what a setting of shutdown is supposed to mean.

The bug is why there are two spurious passes.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel