Re: [xen-unstable test] 153983: regressions - FAIL

[Ian Jackson <iwj@xxxxxxxxxxxxxx>]

osstest service owner writes ("[xen-unstable test] 153983: regressions - FAIL"):
> flight 153983 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/153983/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-arm64-arm64-libvirt-xsm  7 xen-boot                 fail REGR. vs. 
> 152877
> 

Following discussion on irc (see below), I have force pushed this.

> version targeted for testing:
>  xen                  1e2d3be2e516e6f415ca6029f651b76a8563a27c


10:57 <andyhhp__> Diziet: force push on flight 153983?  There was only
                  one failure, and it laxaton1 which went down for
                  reboot and never came back

11:00 <julieng> andyhhp__: This suggests the PCI training failed on
                the board.  This is a known failure that happen time
                to time.
11:03 <andyhhp__> in this case, a force push will unbreak the mess we
                  have with the minios master branch, and should stop
                  the torrent of ovmf build failures
11:05 <julieng> Right, I was just confirming that the bug in laxton1
                can be disregarded (in the past we had to re-flash
                when the board when this happens).

11:10 <Diziet> andyhhp__: Let me look
11:11 <Diziet> julieng: I don't remember it happening recently.  I
               wonder what has changed.

11:13 <Diziet> Well, force pushing that would be betting that if it
               weren't for the laxton boot failure, the test would
               have passed.
11:14 <Diziet> It passed on b11910082d90
11:14 <Diziet> And the difference is     x86/pv: Fix assertions in 
               svm_load_segs()
11:14 <Diziet> OK, sold