Use SAGE_DOC_SRC instead of relative path in docbuilder test

[collares]

These two sage_docbuild tests use a relative path, requiring sage -t --all to be run from a specific directory. This was never needed before, so perhaps it was unintended.

[github-actions]

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

[tobiasdiez]

How do you run into this issue? I.e. why do you have the sage_doctest folder around but not src/doc?

[collares]

@tobiasdiez Yes, you're right. The problem with the new tests is something else: Before, the paths in the relevant tests were prefixed by Path(os.environ['SAGE_DOC_SRC']), while now they use relative paths such as src/doc. Therefore, running the full testsuite (sage -t --all) now needs to be done in a specific working directory, which wasn't the case before. Is that intended?

[tobiasdiez]

@tobiasdiez Yes, you're right. The problem with the new tests is something else: Before, the paths in the relevant tests were prefixed by Path(os.environ['SAGE_DOC_SRC']), while now they use relative paths such as src/doc. Therefore, running the full testsuite (sage -t --all) now needs to be done in a specific working directory, which wasn't the case before. Is that intended?

No this was indeed not intended. Thanks for bringing this up and providing a fix! One small suggestion from my side, otherwise it's good to go.

[collares]

Fixed. Thanks for the review!

[tobiasdiez]

CI issues seem to be unrelated.