On Sep 3, 2012, at 07:05 , Jeroen Demeyer wrote:
Built from scratch on Mac OS X, 10.6.8 (Dual 6-core Xeons), no problems. Testing ('ptestlong') had one failure:
sage -t --long -force_lib devel/sage/sage/rings/polynomial/toy_buchberger.py
The failure occurred because, according to the printout, Singular crashed; it was automatically restarted, and testing continued, with, I think, the correct results, but the output was cluttered with unexpected printouts because of the crash, causing two apparent failures.
I reran the full test, and all tests passed. I can provide crash log and syslog events, if needed.
On Mac OS X, 10.7.4 (Quad core Core i7), the build completed w/o problems. Testing ('ptestlong') ran into the dreaded "timeout in interrupt.py" problem:
sage -t --long -force_lib devel/sage/sage/tests/interrupt.pyx
failed. I noticed that while this "failure" was underway, the python process was chewing up 100% of one core. Not sure what that means, but it might point to something.
Then I reran full tests twice. In each case I got ~6 failures. Since this seemed bizarre to me, I trashed $SAGE_ROOT and reinstalled and rebuilt. This time, the build and the testing ran w/o any problems.
Something evil is lurking in the underbrush, at least according to the pricking in my thumbs...
Justin C. Walker, Curmudgeon at Large
Institute for the Enhancement of the Director's income
What if the hokey pokey
really *is* what it’s all about?