Re: [Xen-devel] [xen-unstable test] 122715: trouble: broken/fail/pass

[Ian Jackson <ian.jackson@xxxxxxxxxx>]

osstest service owner writes ("[xen-unstable test] 122715: trouble: 
broken/fail/pass"):
> flight 122715 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/122715/
> 
> Failures and problems with tests :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-arm64-arm64-xl             <job status>                 broken
>  test-arm64-arm64-xl-xsm         <job status>                 broken
>  test-arm64-arm64-examine      5 host-install           broken REGR. vs. 
> 122580
>  test-arm64-arm64-xl           4 host-install(4)        broken REGR. vs. 
> 122580
>  test-arm64-arm64-xl-xsm       4 host-install(4)        broken REGR. vs. 
> 122580

I have force pushed 858dbaaeda33b05c1ac80aea0ba9a03924e09005, because:

The failures in 122715 were due to the failure of laxton1.  122660 has
no arm64 failures.  Between 122660's xen.git and 122715's, the only
change other than to strictly x86 files was a change to the ACPI
build arrangements:

 858dbaaeda33b05c1ac80aea0ba9a03924e09005
 libacpi: fixes for iasl >= 20180427

That change is very unlikely to cause run-time failures, although
there might be a risk that it would break the build.  However, 122804
included that change and there all the arm64 builds passed.  So on
that basis, we think there are no real regressions here.

There are still a handful of later changes just in staging.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel