-
-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maxima interface chokes randomly #8772
Comments
comment:1
On the following system, with Sage 4.5.3.alpha2.
which is not a cheap PC, but a decent workstation, I see this error 4 times when
was run 100 times. So it's causing The following tests failed one or more times
In each case, although the exact error message is different, I always see:
Dave |
comment:2
Replying to @sagetrac-drkirkby:
I mean there were no reported hardware problems. |
Changed author from Nathan Dunfield to none |
comment:3
I'm removing the 'Author' field, as nobody has actually written anything to solve it yet - or at least if they did, there's nothing on the ticket to indicate they did. Dave |
comment:4
Could you give the exact messages for each of the failed files? |
comment:5
Replying to @qed777:
Sure. I will attach four files
which show the errors on my 21st, 34th, 60th and 90th runs. They correspond to a failure of
Dave |
Attachment: run-21-weightspace.py.txt Failed devel/sage-main/sage/modular/overconvergent/weightspace.py (first of two failures of this test) |
Attachment: run-34-benchmark.py.txt Failed devel/sage/sage/tests/benchmark.py |
Failed devel/sage-main/sage/modular/overconvergent/weightspace.py (second failure) |
Attachment: run-60-weightspace.py.txt Failed devel/sage/sage/calculus/desolvers.py |
comment:6
Attachment: run-90-desolvers.py.txt I was unable to attach the files earlier, as trac was not working correctly (/var was full). Note Alex Ghitza said on sage-devel that Dave. |
comment:7
I could reproduce Nathan's error with Sage 4.5.3.rc0 on Ubuntu 10.04 x86_64 (Core2), but only in conjunction with heavy system load:
(I've added Doctesting in parallel with 32 threads ( I couldn't post this earlier either because of trac errors... ;-) |
comment:8
Replying to @nexttime:
Not really (the run with 64 threads):
The failing tests:
(I think this is ok, as mentioned.)
This might also simply be a timeout.
No idea. I get the same error if I just type that line in Sage. Doctesting the file succeeds... Oh wait, that was the Sage session that gave the Maxima error! After restarting Sage, I get the expected result:
(I exited Sage as usual - with Control-D; just in case you wonder.) |
comment:13
FWIW, the original code in the description no longer calls Maxima in |
comment:15
Again seeing similar failures in #22191 (update ECL to 20.4.24) on Cygwin |
comment:18
Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review. |
Sufficiently many calls to Maxima eventually causes that interface to throw an exception, some samples of which are given below. A minimal piece of code exhibiting this problem is
This error has been observed in Sage 4.3.* on OS X.5.* (8-core Xeon Mac Pro and 2-core Intel Core 2 Mac Book), and Ubuntu Linux 9.10 (quad-core Intel Core 2). See the sage-devel thread http://groups.google.com/group/sage-devel/browse_thread/thread/3b43147e44324c25 for some discussion. In particular, it may be related to #5662 where the synchronization with Maxima was getting lost on certain multi-core CPUs because of something related to switching between cores. It takes some time, e.g. 5-15 minutes for the problem to manifest itself.
Typical errors:
CC: @nexttime @qed777 @dimpase @pjbruin @spaghettisalat
Component: interfaces
Keywords: Maxima
Issue created by migration from https://trac.sagemath.org/ticket/8772
The text was updated successfully, but these errors were encountered: