flight 184831 linux-6.1 real [real]
flight 184840 linux-6.1 real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/184831/
http://logs.test-lab.xenproject.org/osstest/logs/184840/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
flight 184832 linux-5.4 real [real]
flight 184844 linux-5.4 real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/184832/
http://logs.test-lab.xenproject.org/osstest/logs/184844/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
From: Maximilian Heyne
Commit fa765c4b4aed2d64266b694520ecb025c862c5a9 upstream
shutdown_pirq and startup_pirq are not taking the
irq_mapping_update_lock because they can't due to lock inversion. Both
are called with the irq_desc->lock being taking. The lock order,
however, is first
flight 184833 xen-unstable real [real]
flight 184848 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/184833/
http://logs.test-lab.xenproject.org/osstest/logs/184848/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
flight 184835 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184835/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 184816
test-amd64-amd64-xl-qemuu-win7-amd64
flight 184838 xen-4.17-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184838/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-win7-amd64 19 guest-stop fail like 184786
test-armhf-armhf-libvirt 16
Hi,
The link to the last year schedule at
https://events.linuxfoundation.org/archive/2023/xen-project-summit/ is
broken, it opens a page for upcoming "ONE summit" event that doesn't
look to be related to Xen Summit.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
From: Andrew Panyakin
From: Maximilian Heyne
Commit fa765c4b4aed2d64266b694520ecb025c862c5a9 upstream
shutdown_pirq and startup_pirq are not taking the
irq_mapping_update_lock because they can't due to lock inversion. Both
are called with the irq_desc->lock being taking. The lock order,
flight 184862 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184862/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 3955325292f49257797f339cfdcb84748550e069
baseline version:
xtf