On Wed, Feb 8, 2017 at 10:36 AM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Tue, Feb 7, 2017 at 6:49 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: >> On 2017-02-07 17:30, Erik Bray wrote: >>> >>> A problem I've been having lately when running Sage's test suite on >>> Cygwin (i.e. sage -t -a). >>> >>> Several of the tests that use Maxima are spinning up Maxima processes >>> (I guess interacted with via pexpect?) and not killing them. >> >> >> This is probably Cygwin-specific. It would help if you could give some more >> details. For example: is the problem reproducible or does it only happen >> sometimes? Do you know which files cause the problem? Do the doctests >> actually pass? Does Cygwin have something like strace which might help to >> debug this? > > Yes, almost certainly Cygwin-specific. Though I'm not sure when it > started--this didn't happen when I was running the tests a few months > ago. > > It's reproducible insofar as every time I run the full test suite it > happens. I haven't pinpointed any specific tests that cause the > problem--that's mainly what I was asking for help with. I.e. what are > some tests that use Maxima?
To answer this question for myself--as the discussion on what Maxima is used for in Sage pointed me in the right direction--the sage/calculus tests reliably start up at least 3 maxima processes, which then run away with my CPU even after the those tests are finished. I'll see if I can see what exactly they are doing. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
