Hi there, I have a FTBFS that I can't wrap my head around. Maybe some of you have experienced similar weirdness after the mass rebuild. python-PyMuPDF-1.25.1-2.fc42 FTBFS in rawhide according to koschei [1] and koji scratch [2]. Indeed, the build itself succeeds but a test fails because a thread gets aborted. The same version built and tested fine during the mass rebuild [3], and python-PyMuPDF-1.25.1-1.fc42 before [1], with the only difference being the empty mass rebuild bump commit. The main dependency is mupdf-devel-1.25.2-2.fc42 and friends, and again the only before/after change here is the mass release bump; this one does not have a test suite, though, and basically the PyMuPDF tests test mupdf. As you can see in my copr integration testing [4] [5], the same versions worked on all things Fedora/EPEL a month ago. Today I triggered a rebuild of the mass rebuild versions there, and now those same versions build and test fine everywhere except all rawhide chroots. I *think* that the same version worked in mockbuild until a few days ago, but I may be mistaken. It fails now. So what's the difference? Something related to gcc15/swig/llvm, i.e. changed/misbuilt python bindings? A new pytest timeout killing a test? Totally stomped, looking for pointers (huh). Cheers Michael [1] https://koschei.fedoraproject.org/package/python-PyMuPDF?collection=f42 [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=128458691 [3] https://koji.fedoraproject.org/koji/buildinfo?buildID=2631525 [4] https://copr.fedorainfracloud.org/coprs/mjg/mupdf/builds/ [5] https://copr.fedorainfracloud.org/coprs/mjg/python-PyMuPDF/builds/ -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue