Test suite regressions in the meson build

[antonio-rojas]

Meta issue to track test suite regessions with the meson build. The failures happen when running an installed sage - they may not be reproducible when running the test suite from the source tree.

For distro packaging, it is important to run the test suite from an installed sage to make sure everything works properly. Some of the failures may not have any noticeable effect for users, but still cause noise in the test suite that may prevent actual issues from getting noticed.

[tobiasdiez]

In #40158, I've discovered a few more issues. Namely,

sage-runtests --long --warn-long 30.0 --random-seed=195123039357273489794946592323936759837 src/sage/misc/sageinspect.py # 2 doctests failed

Since it's not able to relativize to path in sage_getfile_relative. I cannot reproduce it in an editable install (ci uses non-editable). Looks like the problem is that sage_getfile returns the path to the source folder.

sage-runtests --long --warn-long 30.0 --random-seed=195123039357273489794946592323936759837 src/sage_docbuild/builders.py # 28 doctests failed
sage-runtests --long --warn-long 30.0 --random-seed=195123039357273489794946592323936759837 src/sage_docbuild/sphinxbuild.py # 13 doctests failed
sage-runtests --long --warn-long 30.0 --random-seed=195123039357273489794946592323936759837 src/sage_docbuild/utils.py # 7 doctests failed

Since sage_docbuild is not an installed module. Any opinions about how to fix this best? I really don't want to ship the docbuilding to end-users.

[antonio-rojas]

In #40158, I've discovered a few more issues. Namely,

sage-runtests --long --warn-long 30.0 --random-seed=195123039357273489794946592323936759837 src/sage/misc/sageinspect.py # 2 doctests failed

Since it's not able to relativize to path in sage_getfile_relative. I cannot reproduce it in an editable install (ci uses non-editable). Looks like the problem is that sage_getfile returns the path to the source folder.

Won't those be fixed with cython/cython#6755 ?

sage-runtests --long --warn-long 30.0 --random-seed=195123039357273489794946592323936759837 src/sage_docbuild/builders.py # 28 doctests failed
sage-runtests --long --warn-long 30.0 --random-seed=195123039357273489794946592323936759837 src/sage_docbuild/sphinxbuild.py # 13 doctests failed
sage-runtests --long --warn-long 30.0 --random-seed=195123039357273489794946592323936759837 src/sage_docbuild/utils.py # 7 doctests failed

Since sage_docbuild is not an installed module. Any opinions about how to fix this best? I really don't want to ship the docbuilding to end-users.

I've never tested anything in sage_docbuild. After #40686 I can simply do python -m sage.doctest -a -l to fully test (only) the installed parts of sage.