Jan Beulich writes ("Re: [Xen-devel] [xen-unstable test] 116832: regressions -
FAIL"):
> This is a blue screen, recurring, and has first been reported in flight
> 116779, i.e. was likely introduced in the batch ending in commit
> 4cd0fad645. Among those the most likely candidates appear to be
> the SVM changes (the failures are all on AMD hardware). The logs
> there also have huge amounts of "Unexpected nested vmexit",
> albeit not directly connected with the failed test afaict.
Ian Jackson writes ("Re: [xen-unstable test] 116832: regressions - FAIL"):
> This is the expected Windows failure. Force pushed.
Oops. Sorry about that.
I think this goes to show that (i) leaving known failures languishing
for months and expecting them to be force pushed results in human
error (ii) I should read the whole email thread first.
Sorry,
Ian.
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
