On SuSE, 32-bit, sage -testall -long passes except for errors in the same three files Jaap reported above (and a harmless timeout in elliptic curves).
Craig: thanks for pointing out SAGE_CHECK. But it strikes me that there is no way I can run those tests now, without recompiling the corresponding spkgs from scratch. Is there any way one can get spkgs to provide a test script, separate from the installation procedure, so something like "sage -tspkg flint-xxx.spkg" would run the tests for Flint? David On Jun 27, 9:08 pm, Jaap Spies <j.sp...@hccnet.nl> wrote: > Tom Boothby wrote: > > Sage 4.1.alpha2 has been released, find it at > > >http://sage.math.washington.edu/home/boothby/releases > > > As with 4.1.alpha1, there are two known doctest failures. One is very > > simple to fix, and the other might be tricky. I made an attempt at > > solving them, but William claims that my fix will break osx10.4. I'd > > appreciate it if somebody could take a look at this. > > On Fedora 9, 32 bit: > > ---------------------------------------------------------------------- > The following tests failed: > > sage -t "devel/sage/doc/fr/tutorial/programming.rst" > sage -t "devel/sage/sage/graphs/graph.py" > sage -t "devel/sage/sage/misc/darwin_utilities.pyx" > > Jaap --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
