Use python3 -m sage.doctest in doctest results report if not using sage-runtests

[antonio-rojas]

Instead of sage -t, which no longer works with meson

[github-actions]

Documentation preview for this PR (built with commit 7ff88f2; changes) is ready! 🎉
This preview will update shortly after each push to this PR.

[tobiasdiez]

Why change it from sage -t to sage-runtests?

[antonio-rojas]

Just to minimize the wrapping layers - I didn't make it python3 -m sage.doctest unconditionally because sage may not be installed in the system python namespace

[tobiasdiez]

okay!

[tobiasdiez]

CI is failing now, seems like a typo in the merge resolution.

[antonio-rojas]

CI is failing now, seems like a typo in the merge resolution.

Thanks, fixed.

[antonio-rojas]

Follow-up at #40704

[vbraun]

The test failures are now reported as

sage-runtests --long --warn-long 30.0 --random-seed=0 src/sage/misc/sagedoc.py  # 1 doctest failed

which isn't a command that I can easily run from the repo root. IMHO thats a definite regression, it is much clearer to output a command that you can just run to re-run the test

[antonio-rojas]

The test failures are now reported as

sage-runtests --long --warn-long 30.0 --random-seed=0 src/sage/misc/sagedoc.py  # 1 doctest failed

which isn't a command that I can easily run from the repo root. IMHO thats a definite regression, it is much clearer to output a command that you can just run to re-run the test

That's easy to change, but note that, depending on your PATH, sage -t may stop working after #39030 (if the first sage found is the compiled one). Would printing the full path to sage-runtests be OK?

[vbraun]

a full path would be ok with me, I don't understand why we need a different command though (but then thats arguably less important)

[tobiasdiez]

What about the relative path from the root? So src/bin/sage-runtests ? I think it's most common to execute stuff from the root, at least CI is doing this.

[antonio-rojas]

#40746