Hi David and John, On 31 Mrz., 11:58, daveloeffler <dave.loeff...@gmail.com> wrote: > Both John Cremona and I have been having some serious problems with > "sage -t" in 3.4.1.alpha0. > > Doing "sage -testall" seems to work as it should, but doctesting a > single file fails horribly in many cases, even with files that weren't > changed at all between 3.4 and 3.4.1.alpha0: > > da...@groke:~/sage-current/devel/sage/sage/modular/modform> sage -t * > [ lots of error output ] > The following tests failed: > > sage -t "constructor.py" > sage -t "eisenstein_submodule.py" > sage -t "element.py" > sage -t "hecke_operator_on_qexp.py" > sage -t "space.py" >
I have no Sage install right now available. Could you check out whether "all is fine" using absolute path names? More precisely, try doing: sage -t /Users/davidloeffler/sage/sage-3.4.1.alpha0/sage-current/devel/ sage/sage/modular/modform/* (with the appropriate absolute path, of course --- I guessed a Mac OS X like absolute path here). If things are OK then, the brokenness should easily be healable around line 681 of the (current) "sage-test" script. (And you may continue to work using this work-around.) Cheers, gsw > None of these failed in 3.4; I did extensive development work on > modular forms based on 3.4 and everything passed. > > This seems to be something to do with trac #2129, "implement "sage -t" > for .spyx files", which was merged in 3.4.1.alpha0. It seems to have > broken doctesting for .py files at the same time. > > David --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
