(+Ian and Stefano)
Hi,
On 10/24/19 8:13 AM, Jürgen Groß wrote:
On 24.10.19 08:47, osstest service owner wrote:
flight 143061 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/143061/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm <job
status> broken
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 4
host-install(4) broken REGR. vs. 142750
Why is Linux kernel 5.4.0-rc4 being used for testing xen-unstable here?
Or am I reading the logs wrong?
test-arm64-arm64-examine 11 examine-serial/bootloader fail REGR.
vs. 142750
I'm not sure what has gone wrong here? The serial logs seem to be fine
for me, but maybe I'm missing something?
This is a known issue on rochesters for the past 6 months (see [1]). In
short, Osstest is checking the sanity of the platform by adding cookie
in the bootloader output. However, this cookie is lost.
Stefano promised to investigate it back then. Last time I heard, he had
access to the colo. Stefano where are we with this?
Cheers,
[1] https://lists.xen.org/archives/html/xen-devel/2019-05/msg00018.html
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
