Never mind -- I remembered the existence of "sage -t -verbose" and found the problem. (It was because I had a comment in my file containing an unmatched opening triple quote -- this somehow throws out the doctest script's parser.)
David On Apr 10, 12:03 pm, daveloeffler <dave.loeff...@gmail.com> wrote: > I've been working on improving doctest coverage in the sage/modular > directory, and I've hit a very curious problem. I added a new doctest > to a file -- sage/modular/hecke/hecke_operator.py, if it matters -- > and ran "sage -t" with the output line of the doctest blank, meaning > to copy the correct output out of the test failure message. > > But it passed, and now I can't seem to get any doctests in this file > to fail! Even if I insert random garbage into the code, it still > passes "sage -t". Other files that depend on this one fail; but this > one still claims to work (even though if I run the tests from a Sage > prompt they fail, as they should). > > Does anybody know how this can have happened? What could be making > "sage -t" return "All tests passed", when the file is deliberately > totally broken? I've tried deleting all the temporary .doctest_foo.py > files from SAGE_ROOT/tmp/, but that doesn't help. > > (It may be something to do with the fact that I had a "sage -t *" > running for the whole sage/modular directory and I interrupted it with > Ctrl-C; has that somehow left temporary files lying around that I > should delete? If so, which ones?) > > 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 -~----------~----~----~----~------~----~------~--~---
