+1 on disabling all doctests that randomly fail. https://github.com/sagemath/sage/pull/39100 might be helpful in discovering these flaky tests.
Do you also want to disable CI workflows that sometimes fail for intrinsic reasons? For example, the Build & Test workflow often fails to push the temporary Docker image that it builds (eg https://github.com/sagemath/sage/actions/runs/13036220999/job/36367766912). On Friday, January 31, 2025 at 12:29:33 AM UTC+1 Kwankyu Lee wrote: > On Friday, January 31, 2025 at 2:44:39 AM UTC+9 dim...@gmail.com wrote: > > You can just check whether CI failures are relevant to your branch, > and if not, write so in comments. > > > I think we should adopt a policy that promptly (no excuse) disable any CI > check that fails due to reasons unrelated to a PR. Disable and enabling a > workflow (CI check) may be done through PRs as well. > > The current practice ignoring erroneous CI checks is degrading the quality > of developer life. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/03e8e509-5de4-402a-a78b-16d27d9f7876n%40googlegroups.com.
