[xen-unstable test] 187884: tolerable FAIL

2024-09-28 Thread osstest service owner
flight 187884 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/187884/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 187869 test-amd64-amd64-xl-qemuu-ws16-amd64

[libvirt test] 187886: tolerable all pass - PUSHED

2024-09-28 Thread osstest service owner
flight 187886 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/187886/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 187865 test-amd64-amd64-libvirt 15 migrate-s

[qemu-mainline test] 187887: regressions - FAIL

2024-09-28 Thread osstest service owner
flight 187887 qemu-mainline real [real] flight 187890 qemu-mainline real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/187887/ http://logs.test-lab.xenproject.org/osstest/logs/187890/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be

Re: [RFC PATCH 05/28] x86: Define the stack protector guard symbol explicitly

2024-09-28 Thread Brian Gerst
On Wed, Sep 25, 2024 at 2:33 PM Uros Bizjak wrote: > > On Wed, Sep 25, 2024 at 5:02 PM Ard Biesheuvel wrote: > > > > From: Ard Biesheuvel > > > > Specify the guard symbol for the stack cookie explicitly, rather than > > positioning it exactly 40 bytes into the per-CPU area. Doing so removes > >

[linux-linus test] 187882: tolerable FAIL - PUSHED

2024-09-28 Thread osstest service owner
flight 187882 linux-linus real [real] flight 187888 linux-linus real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/187882/ http://logs.test-lab.xenproject.org/osstest/logs/187888/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-