Re: Fedora Mass Rebuild 41 has completed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



AFAIK the SIGABRT is thrown from assert. I already have increased the timeout multiplier (meson's command line option) but as I saw this now also happen for x86 I have started to think it is not about the timeout.

It is not a long time ago that I was tracking done another sporadic failure in chatty's tests [1] which actually turned out to be issue in evolution-data-server.

-Tomi

[1] https://gitlab.gnome.org/World/Chatty/-/issues/835#note_2086408

On ti, heinä 30 2024 at 11.40.55 +02:00:00, Michael J Gruber <mjg@xxxxxxxxxxxxxxxxx> wrote:
Am Mo., 29. Juli 2024 um 20:11 Uhr schrieb Tomi Lähteenmäki <lihis@xxxxxxxxx>:
On ma, heinä 22 2024 at 12.43.30 -07:00:00, Kevin Fenzi <kevin@xxxxxxxxx> wrote: The mass rebuild was done in a side tag (f41-rebuild) and moved over to f41. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f41-failures.html I saw "chatty" has failed to build [1] for s390x due test failure. From Koshcei I recently noticed that the same test fails sporadically on almost all arches with the same error.. Can someone trigger a re-build or can I do it myself? Also, if someone happens to know about the assertion error seen in the test [2], please let me know! I have been a little too busy lately so I haven't had yet time to debug it so any hints are appreciated. -Tomi [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=120642410 [2] https://kojipkgs.fedoraproject.org//work/tasks/2504/120642504/build.log
That one is `killed by signal 6 SIGABRT`, apparently after taking longer than the other tests. I have witnessed similar (?) heisenbugs with test suites which include a "kill after timeout"; the tests typically take longer on s390x, even longer for koschei builds than regular ones (??). Maybe there's a timeout which you can increase easily? Cheer Michael
--
_______________________________________________ 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
-- 
_______________________________________________
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux