severity 1111954 normal forwarded 1111954 https://codeberg.org/fibers/fibers/issues/127 thanks
As far as I can tell, all flaky debci checks have now been marked as flaky and does not trigger debci FAIL any more after 1.4.0-1, so I'm hoping we can lower the severity of this now. Fixing the flaky tests have been reported upstream: https://codeberg.org/fibers/fibers/issues/127 I suspect this may take time to fix, as it could be several different underlying bugs, and could be kernel/arch/libc-related. Builds are still flaky due to this problem, but the buildd's appear to re-schedule builds and eventually succeeds. We could silence 'make check' failure during builds too if necessary. I'm not sure what the best recommended way to deal with flaky build failures. Having them FAIL but eventually succeeds allows us to more easily catch which self checks and which platforms fail, which may result in some pattern developing, and help with upstream bug reporting. But if this is an annoyance we can do something like: override_dh_auto_test: -dh_auto_test or something fancier if there is some subset of tests that actually always manages to succeed (as suggested by those debian/tests/control tests without the flaky mark). /Simon
signature.asc
Description: PGP signature
