On Jan 27, 2008 8:03 PM, Justin C. Walker <[EMAIL PROTECTED]> wrote: > > > On Jan 27, 2008, at 24:55 , mabshoff wrote: > > > Sage 2.10.1.rc0 was nothing to write home about, but 2.10.1.rc1 > > should be much better and build out of the box on Linux, OSX 10.4 > > and 10.5. Since rc0 we merged 15 patches, some of them quite > > invasive. So if you review a patch and/or bundle please make > > sure it applies cleanly against this release. > > > > As you can see from the ToDo list there is still some way to > > go before 2.10.1, unless we want to do a release now, i.e. in > > the next 24 hours. In that case we need to fix the notebook > > issue, which I didn't have time to work on yet, but that can be > > resolved by downgrading the TLS components. Another possibility > > is to solve some more issue, do a release by Wednesday. In either > > case we should do 2.10.2, a conservative bug fix only release, > > by Saturday or Sunday. Thoughts? > > > > The tarball [201MB] is available at > > > > http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/ > > sage-2.10.1.rc1.tar > > Built w/o problems on both Mac OS X, 10.4.11 and 10.5.1. One test > failed on each: > > 10.4.11 (Dual Quad Xeon, "-j6"): > > real 80m54.727s > user 64m0.940s > sys 37m8.340s > > > ---------------------------------------------------------------------- > The following tests failed: > > > sage -t devel/sage-main/sage/interfaces/sage0.py > Total time for all tests: 3117.0 seconds > > 10.5.1 (Core Duo, "-j2"): > real 126m1.604s > user 96m4.584s > sys 19m13.760s > > > ---------------------------------------------------------------------- > The following tests failed: > > > sage -t devel/sage-main/sage/interfaces/sage0.py > Total time for all tests: 3000.3 seconds > > In both cases, the 'sage0' failure was the same as Jaap reported for > alpha2 (escape sequences causing syntax errors). I'm not sure I got > the whole thread, though: was there a solution to this?
No, I think everybody is stumped. Interestingly, I just did a full doctest and build on a bunch of different linux machines *and* on osx 10.4 ppc, osx 10.4 intel, osx 10.5 intel, and unfortunately on *none* of them did I see this sage0.py bug. So what do you, Jaap, and Craig Citro all have in common? And can you replicate the sage0.py bug if you very carefully log in as a different user with no .bash* stuff and doctest that file? - 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 -~----------~----~----~----~------~----~------~--~---
