On Mar 5, 2008, at 7:55 AM, mabshoff wrote:
> The merge goes on. 2.10.3.rc2 can be found at > > http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.3/ > sage-2.10.3.rc2.tar Built on two 10.4 systems, with slightly different results. The build succeeded in each case, but the testing showed different results: 10.4.11/Dual Quad Xeon ("-j6"): real 75m37.868s user 60m17.825s sys 31m40.297s The following tests failed: sage -t devel/sage-main/sage/matrix/matrix_symbolic_dense.pyx sage -t devel/sage-main/sage/modular/modsym/space.py sage -t devel/sage-main/sage/plot/plot.py sage -t devel/sage-main/sage/rings/polynomial/groebner_fan.py Total time for all tests: 2775.1 seconds as did the tests for tut.tex and const.tex. 10.4.11/Core 2 Duo ("-j2"): real 106m14.593s user 77m0.740s sys 26m35.990s The following tests failed: sage -t devel/sage-main/sage/matrix/ matrix_symbolic_dense.pyx sage -t devel/sage-main/sage/plot/plot.py sage -t devel/sage-main/sage/rings/polynomial/ groebner_fan.py Total time for all tests: 3670.7 seconds as did the tests for tut.tex and const.tex. Why the 'modsym' failure occurs on one system and not the other, I'm not sure (it is a Linbox failure, apparently). The first log is at sage.math.washington.edu:~justin/logs/2.10.3.rc2.log The second is at sage.math.washington.edu:~justin/logs/2.10.3.rc2-1.log Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Absorption of Federal Funds -------- If you're not confused, You're not paying attention -------- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
