-
-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sage_docbuild: fails when cache cannot be saved #33064
Comments
New commits:
|
Commit: |
Author: Gonzalo Tornaría |
comment:2
A related but independent issue is that several methods whose main purpose is to return a path (e.g. I wonder if it would make sense to ignore |
comment:3
Replying to @tornaria:
Or else maybe tag these doctests with |
comment:4
I'd say these tests should probably not write into the production environment... |
comment:6
Replying to @mkoeppe:
Running tests on a read-write directory creates all of this:
Failure to write Also created on a test run are: |
comment:7
See #22062 for |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:9
Followup on #33085 for the task that doctests pass when html documentation is not built/installed. |
comment:10
The change makes sense to me, but I don't understand the situation in which this will arise. I made the directory |
comment:11
Replying to @jhpalmieri:
Make sure the directory This seems to be a cache of filenames or something... that is computed (or retrieved if cache file present) by For me I think what triggered this is: I build and doctest sagemath before packaging (in that check I have write permission). The package gets installed in a live system at Note that I'm building with |
Reviewer: John Palmieri |
comment:12
I still can't reproduce this, but as I said, the change makes sense. |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. This was a forced push. New commits:
|
comment:14
Rebased to 9.5.rc0 without change. |
comment:15
That doesn't fix anything for me in terms of doctests failure after install in a read only location.
Both fail because they try to create |
comment:16
Does #33085 help? The fix on this ticket was for a very specific problem. |
comment:17
Replying to @jhpalmieri:
No, I have both included. The label |
comment:18
+1 on investigating whether |
comment:19
Replying to @mkoeppe:
Short answer: no Long answer: a "doctrees" folder is passed to the sphinx app, but it is a temporary one. The relevant lines in
So, a temporary "doctrees" folder is used by sphinxify and it has no relationship with what is normally in Grepping sage's source for "doctrees" returned a false positive in that case. |
comment:20
Thanks! I've added this to #29868. |
Changed branch from u/tornaria/sage_docbuild-save_cache to |
When doctesting
src/sage_docbuild/__init__.py
on a read-only location we get a failure which ultimately boils down to:This is due to a
save_cache()
method trying to save into that file; I believe it would be harmless to ignore this permission error (if the cache is not saved, it will have to be regenerated, so what).CC: @jhpalmieri
Component: doctest framework
Author: Gonzalo Tornaría
Branch/Commit:
e89193f
Reviewer: John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/33064
The text was updated successfully, but these errors were encountered: