On Tue, Jan 21, 2025 at 9:07 PM Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > > Consider https://kojipkgs.fedoraproject.org/mass-rebuild/f42-failures.html: > there are 7 failed rust packages there. Part of the reason is that > by not bundling we don't have a long tail of old versions stashed > in other projects. Possibly also worth noting: Of those six (I only found 6) failed rust-* packages, I already knew that they would fail beforehand (or, if they failed, I would likely know why): - rust-ascii: failing test since Rust 1.84 because of a behaviour change in converting string to integer with arbitrary radixes - rust-below-common: known flaky test (date/time related test fails when run between 00:00 and 01:00 for some reason) - rust-sequoia-chameleon-gnupg: known test failure that I have already reported upstream, fixed already in upstream git - rust-temp_env: known flaky test, re-running this should resolve the failure The two failures I *didn't* know about prior two the mass rebuild: - rust-colorgrad: looks like an update was pushed that caused a patch to fail to apply so it was never built prior to the mass rebuild - rust-hyper-timeout: looks like a timeout, re-running the build should resolve this I think All of these should be trivial to fix (either by adjusting tests or just resubmitting package builds with known flaky test suites), or by adapting the patch that was not correctly rebased. Two additional Rust-written packages of mine failed the mass rebuild, one was a flaky build failure that was resolved by resubmitting the build, and the other is a known test failure with Rust 1.84 that should be easy to resolve as well, and I plan to do that when submitting the next update. I keep an eye on the koschei status for all rust-* packages, so it's very rare that there are more than like > 3 known FTBFS packages in rawhide at any point in time (maybe except for after Rust compiler updates that add new error-by-default lints). And even so, watching out for new build failures is probably the *smallest* part of the work I do for the Rust SIG ... Fabio -- _______________________________________________ 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
