Doctesting in parallel

[kcrisman]

Dear support,

According to various places (including William's Barcelona dev talk),
you should be able to doctest in parallel:

sage -tp 3 "devel/sage/sage/module/file.py"

But this doesn't work for me. Instead, I get a message about
doctesting 0 files in parallel, and of course all 0 tests pass very
quickly indeed. Removing the quotes doesn't work, and

sage -t "devel/sage/sage/module/file.py"

works fine. What am I doing wrong? And can someone add documentation
about the exact syntax, if not? Unfortunately I don't know what to
do ?? to in order to get information about the various options one can
pass to ./sage as a command.

Thanks! This could make life a lot easier, or at least waste less
time.

- kcrisman

[kcrisman]

"Testing them all using one thread would take a few hours." Why, yes,
it did!

I see the problem. I was running the command from my home directory,
but testing files in a nonexistent devel/sage in my home directory.
Maybe you can add something like that for those of us who don't
necessarily cd into sage-x.x.x/ before running commands? Thanks!

- kcrisman


>
> I have written some documentation at
>
> http://mvngu.wordpress.com/2009/09/05/parallel-testing-the-sage-library/
>
> Hope that helps.
>
> --
> Regards
> Minh Van Nguyen

[kcrisman]

By the way, why doesn't that cause a problem when it's just the -t
flag?

- kcrisman

[David Joyner]

On Sat, Sep 5, 2009 at 1:40 AM, Minh Nguyen<nguye...@gmail.com> wrote:
>
> Hi kcrisman,
>
> On Sat, Sep 5, 2009 at 2:24 AM, kcrisman<kcri...@gmail.com> wrote:
>
> <SNIP>

>
>> works fine.  What am I doing wrong?  And can someone add documentation
>> about the exact syntax, if not?
>

> I have written some documentation at
>
> http://mvngu.wordpress.com/2009/09/05/parallel-testing-the-sage-library/
>
> Hope that helps.

This is useful. Could this be added to the wiki and/or the programming manual?

[kcrisman]

> > By the way, why doesn't that cause a problem when it's just the -t
> > flag?
>

> I don't understand your question. Can you please explain?

For me, running (from the home directory)

sage-x.x.x/sage -t "devel/sage/sage/myfile.py"

works, but

sage-x.x.x/sage -tp 3 "devel/sage/sage/myfile.py"

does not, as I have to change directories to sage-x.x.x/sage first.
Why the difference? Just for clarification - I'm not suggesting
anyone really knows why, but it's a little weird.

- kcrisman