id summary reporter owner description type status priority milestone component resolution keywords cc merged author reviewer upstream work_issues branch commit dependencies stopgaps
5155 Fix doctests and methods that want write access to $SAGE_LOCAL Michael Abshoff Jeroen Demeyer "All doctests in Sage should pass when they are run as a user that does not have write access to the Sage install. To do that, set SAGE_TESTDIR to some place writable, for example
{{{
export SAGE_TESTDIR=$HOME/tmp
}}}
and run the doctests on a Sage install that isn't owned by the user:
{{{
$ ./sage -tp 6 devel/sage/doc/common devel/sage/doc/de devel/sage/doc/en devel/sage/doc/fr devel/sage/doc/ru devel/sage/sage
}}}
Here, we assume that the owner of the Sage install has run Sage at least once (or has applied #11926) and has ran some doctest.
On sage-4.7.2.alpha4, this causes the following failures:
{{{
sage -t -long devel/sage/sage/matrix/matrix2.pyx # 1 doctests failed
sage -t -long devel/doc/tut/tut.tex # 5 doctests failed
sage -t -long devel/sage/sage/interfaces/qepcad.py # 2 doctests failed
sage -t -long devel/sage/sage/plot/plot.py # 6 doctests failed
sage -t -long devel/sage/sage/databases/database.py # 1 doctests failed
sage -t -long devel/sage/sage/calculus/calculus.py # 1 doctests failed
sage -t -long devel/sage/sage/misc/package.py # 1 doctests failed
sage -t -long devel/sage/sage/gsl/ode.pyx # 4 doctests failed
sage -t -long devel/sage/sage/server/support.py # 1 doctests failed
sage -t -long devel/sage/sage/server/notebook/notebook.py # 1 doctests failed
sage -t -long devel/sage/sage/server/notebook/twist.py # 8 doctests failed
sage -t -long devel/sage/sage/structure/sage_object.pyx # 6 doctests failed
}}}
" defect needs_work critical sage-4.7.2 doctest Luis Felipe Tabera Alonso Mike Hansen N/A #11926