On 02.06.2023 05:21, osstest service owner wrote:
> flight 181082 linux-linus real [real]
> flight 181098 linux-linus real-retest [real]
> http://logs.test-lab.xenproject.org/osstest/logs/181082/
> http://logs.test-lab.xenproject.org/osstest/logs/181098/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-armhf-armhf-xl-credit1   8 xen-boot                 fail REGR. vs. 
> 180278

Following up from yesterday's discussion, I've noticed only now that
we had an apparently random success once in mid April. Without that,
we'd see ... 

> Tests which did not succeed, but are not blocking:
>  test-armhf-armhf-examine      8 reboot                       fail  like 
> 180278
>  test-armhf-armhf-xl-arndale   8 xen-boot                     fail  like 
> 180278
>  test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stop            fail like 
> 180278
>  test-amd64-amd64-xl-qemuu-win7-amd64 19 guest-stop            fail like 
> 180278
>  test-armhf-armhf-xl-credit2   8 xen-boot                     fail  like 
> 180278
>  test-amd64-amd64-qemuu-nested-amd 20 debian-hvm-install/l1/l2 fail like 
> 180278
>  test-amd64-amd64-xl-qemuu-ws16-amd64 19 guest-stop            fail like 
> 180278
>  test-armhf-armhf-xl-multivcpu  8 xen-boot                     fail like 
> 180278
>  test-armhf-armhf-libvirt-raw  8 xen-boot                     fail  like 
> 180278
>  test-armhf-armhf-libvirt      8 xen-boot                     fail  like 
> 180278
>  test-armhf-armhf-libvirt-qcow2  8 xen-boot                    fail like 
> 180278
>  test-armhf-armhf-xl           8 xen-boot                     fail  like 
> 180278
>  test-armhf-armhf-xl-vhd       8 xen-boot                     fail  like 
> 180278
>  test-armhf-armhf-xl-rtds      8 xen-boot                     fail  like 
> 180278

that singular test in the same group as all the other armhf ones. I
wonder whether we shouldn't try to get those in sync. Which direction
depends - aiui a force push would allow subsequent automatic pushes
if only the armhf tests fail. Whereas clearing the "fail like" state
for all of them would give a better picture of what's actually
broken right now.

Jan

Reply via email to