OK, sorry, as usual for me I mixed up sympy and scipy :-) yes, trac tickes became github PRs.
On Sun, 24 Sept 2023, 12:23 Oscar Benjamin, <[email protected]> wrote: > On Sun, 24 Sept 2023 at 09:50, Dima Pasechnik <[email protected]> wrote: > > > > On Sun, Sep 24, 2023 at 9:21 AM Tirthankar Mazumder > > <[email protected]> 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. > > We're talking about this: > > https://github.com/sympy/sympy/blob/master/.github/workflows/ci-sage.yml > https://github.com/sympy/sympy/actions/runs/6284388889/job/17065717301 > > Before the GitHub transition this CI job was set to test the master > branch of SymPy against a particular trac ticket. The trac ticket > would hold the changes needed for Sage to update to the next SymPy > versions. When this CI job was working properly I submitted updates to > the trac ticket (mostly just updating doctests) so that Sage was ready > to update to the next SymPy version. The job is useful if it usually > passes so that we can see when a change in SymPy breaks something but > it just fails all the time right now. > > I'm not sure what the equivalent of that trac ticket would be now (a > pull request somewhere?) or how to set up the CI job so that it can > track that ticket. > > Mostly the changes needed before were to do with changes in SymPy's > printing output and also Laplace transform calculations. The Laplace > transform code in SymPy has largely been rewritten in recent releases > including significant changes to inverse_laplace_transform since the > last release that have not been tested against Sage as far as I know. > Probably some Sage doctests need to be updated already. > > -- > Oscar > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/CAHVvXxTQ_eazEZyaM%3Dz4oZYoup4rEWfhg0BXFNyLZ9%3Dy7DDOXg%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq0o24y%3D-v1PUu2GzKqY5kpT%2BB1LcuWReFrYgeenFhmFmg%40mail.gmail.com.
