On Sun, Sep 24, 2023 at 9:21 AM Tirthankar Mazumder <greenwoodt...@gmail.com> wrote: > > Sorry to resurrect such an old thread, but the Sage CI is failing for SymPy > again. This time, it looks to me like the issue is the fact that GitHub > Actions is trying to pull the Sage code from trac, which shouldn't be > happening because SageMath moved to GitHub some time back.
Which actions are you referring to? Something here: https://github.com/scipy/scipy/actions ? Somewhere else? Please point out at concrete GitHub Actions where you see this. > > Can somebody please update the Sage CI for SymPy so that it works? > > Regards, > Tirthankar Mazumder > > On Wednesday, July 6, 2022 at 4:10:13 AM UTC+5:30 Matthias Koeppe wrote: >> >> Fixed in https://github.com/sympy/sympy/pull/23728 via >> https://trac.sagemath.org/ticket/34118 >> >> On Tuesday, July 5, 2022 at 1:01:48 PM UTC-7 greenw...@gmail.com wrote: >>> >>> In the SymPy GitHub repository, currently the only CI jobs that are failing >>> are the Sage CI ones. I was investigating the workflows, and found that >>> there are many instances of this warning: >>> make -j8 build/make/Makefile --stop >>> make[1]: Entering directory '/sage' >>> make -j8 build/make/Makefile --stop >>> make[2]: Entering directory '/sage' >>> make[2]: warning: -j8 forced in submake: resetting jobserver mode. >>> make -j8 build/make/Makefile --stop >>> make[3]: Entering directory '/sage' >>> make[3]: warning: -j8 forced in submake: resetting jobserver mode. >>> make -j8 build/make/Makefile --stop >>> make[4]: warning: -j8 forced in submake: resetting jobserver mode. >>> >>> This error is repeated more than 5000 times, and then bash finally kills >>> the process. >>> >>> According to this StackOverflow answer, to silence this warning, the number >>> of jobs have to stay at the default number. I investigated some of the >>> uploaded artifacts, and found the lines >>> ARG NUMPROC=8 >>> ENV MAKE="make -j${NUMPROC}" >>> in the Dockerfile uploaded in the logs. >>> >>> While I am not sure whether this is the source of the error or not, >>> silencing this warning should make finding the root issue easier. I was >>> unable to figure out how this Dockerfile is constructed, so I am sharing my >>> findings here. >>> >>> Regards, >>> Tirthankar Mazumder > > -- > 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 on the web visit > https://groups.google.com/d/msgid/sage-devel/fa45c22e-f080-4510-b319-8de945c64920n%40googlegroups.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 on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq1miscwCWPotr_SbCwefo0OmK9CtcPLrX0ppAbXnYMc8g%40mail.gmail.com.
