On Tue, Sep 23, 2008 at 11:12 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Sep 23, 5:37 am, Dan Drake <[EMAIL PROTECTED]> wrote: >> On Wed, 17 Sep 2008 at 08:55PM -0700, mabshoff wrote: > > Hi Dan, > >> > > but when I run 'make test', some test will simply stop. This happens >> > > every time, and often with different tests. The CPU usage is zero, >> > > and nothing happens. The test just sits there. >> >> > You can log the Sage<->Maxima communication and we can then poke >> > around. Another thing is to run say calculus.py under -verbose and >> > attempt to narrow it down. >> >> I was going to ignore that problem and just use a precompiled >> binary...but I was getting similar problems with that when I did a lot >> of calculus. So I'm hoping to understand this problem better. > > Ok. > >> I've run doctests on calculus.py, and most of the time it finishes, but >> sometimes it hangs. Using -verbose doesn't help; it gets to some test >> and just waits. If I kill the relevant lisp.run process, the testing >> will continue and report the failure. > > This looks like some synchronization issue. > >> How I can log the Sage-Maxima communication? Does anyone know more about >> this problem? > > You can give the interface an optional log parameter. But I don't have > a patch at the moment, give me a while if you still have problems. >
This is slightly OT, but Michael would you like it to so that one could more easily turn on logging of the interfaces? If so, what would be your dream interface? Setting an environment variable? What would happen? William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
