#8772: Maxima interface chokes randomly
-------------------------------+--------------------------------------------
Reporter: dunfield | Owner: was
Type: defect | Status: new
Priority: critical | Milestone: sage-4.5.3
Component: interfaces | Keywords: Maxima
Author: Nathan Dunfield | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Changes (by drkirkby):
* cc: leif, mpatel (added)
Comment:
On the following system, with Sage 4.5.3.alpha2.
* Sun Ultra 27
* 3.33 GHz Intel Xeon W3580 CPU. 4 cores. 8 threads. (Hyperthreaded)
* 12 GB of ECC DDR3 RAM
* 2 x 500 GB disks (both mirrored)
* 2 x 2 TB disks (both mirrored)
* ZFS 128-bit file system, which should detect and correct errors
* !OpenSolaris 06/2009.
which is not a cheap PC, but a decent workstation, I see this error 4
times when
{{{
make ptestlong
}}}
was run 100 times. So it's causing {{{make ptestlong }}} to fail in 4% of
cases for me. Since this machine is hyperthreaded and has 4 cores, 8
threads would be run when the doctests were run. I've checked the system
logs and there are now reported hardware problems.
The following tests failed one or more times
{{{
devel/sage-main/sage/modular/overconvergent/weightspace.py (twice)
devel/sage/sage/tests/benchmark.py (once)
devel/sage/sage/calculus/desolvers.py (once)
}}}
In each case, although the exact error message is different, I always see:
{{{
Premature termination of input
}}}
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8772#comment:1>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
