On Tue, Feb 7, 2017 at 11:30 AM, Erik Bray <erik.m.b...@gmail.com> 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. And > what's worse, is that each one seems to sit in a busy wait. So even > once the test suite has long since moved on to other tests I'm left > with dozens of maxima processes chewing up my CPU for nothing. I can > kill them manually and it doesn't seem to break any tests. > > But in the meantime, can anyone point me in the right direction to > look for what might be causing this? It seems to only be maxima > that's the problem. Other pexpect interfaces don't leave processes > running (much less eating up CPU).
Basic question: is there any reason whatsoever for us to even have a pexpect interface to maxima anymore? Nils Bruin (and others) put a massive amount of effort into a C library version (using ecl) over the years... > > Thanks, > Erik > > -- > 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. -- William (http://wstein.org) -- 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.
