You can just check whether CI failures are relevant to your branch, and if not, write so in comments.
On Thu, Jan 30, 2025 at 11:35 AM Jackson Walters <jacksonwalt...@gmail.com> wrote: > > Hello, > > I'm attempting to finish two pull requests: > > https://github.com/sagemath/sage/pull/38455 > https://github.com/sagemath/sage/pull/39200 > > They do depend on one another in that 38455 requires extend=true from 39200. > However, right now both PRs seem to be passing all the major "build and test" > CI checks, but a few (three for each) appear to be "flaky" in that they don't > seem to actually be indicating anything is wrong with the code, nor that > there is anything I can change to get them to pass. > > Is this just a matter of triggering the checks repeatedly with empty commits > until such time that the issues surrounding the offending checks are resolved? > > Any help would be appreciated. > > Thanks, > Jackson > > -- > 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/CAGqtwVDMMMxa45C2kGNThzDWGZSJ936ReCN2ViKHSeS2qngy9A%40mail.gmail.com. -- 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/CAAWYfq3m78iGCVhrD%3DWBqntR-DeCvW8eaiMmdSSfvUxeEs2SzA%40mail.gmail.com.
