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
git-related doctest failures after moving sage installation #15901
Comments
comment:1
FYI: A manual fix is to use
to rebuild git. |
comment:2
Replying to @dkrenn:
Or just
|
Branch: u/jhpalmieri/git-relocate |
comment:4
Here's an attempt at a patch. Works for me. New commits:
|
Commit: |
Author: John Palmieri |
comment:5
How do you compile sage after this?
does not work. Even the following doesn't work
|
comment:6
Replying to @ppurka:
You have to touch the (I think.) |
comment:7
Ahem, or maybe something else... 8-) |
comment:8
Hmm. I guess I should have said "Worked for me yesterday on one machine." I can't get it to work today on a different machine (and haven't tried on the first one yet). |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
Okay, here's another attempt. Please try this one. (I hope that just |
comment:12
This must explain the failures in the first patchbot run of 6.2 ( |
comment:13
The patchbot instance is now getting doctest failures in
The directory it is looking in is where my other Sage copy was before moving that copy to test this ticket! The path seems to have been obtained from a cache living in my home directory: |
comment:14
Curiously, sometime after the above failures in |
Reviewer: Peter Bruin |
comment:15
Replying to @pjbruin:
... which should be enough for a positive review. If there really is a problem with the |
comment:16
Replying to @pjbruin:
Then we should probably also change the ticket's title accordingly. |
comment:17
Replying to @pjbruin:
This really deserves its own ticket (and btw. is pretty unrelated to relocating Sage; just imagine having different versions of Sage running at the same time). IMHO Sage's matplotlib must not put its cache into |
comment:18
Replying to @nexttime:
... or probably |
comment:19
Does it need to be writeable? Anyway, it looks like we can modify this by setting the environment variable |
comment:20
Replying to @nexttime:
In fact that is where it used to be: I have an old directory |
comment:21
By default, Sage's matplotlib should write to |
comment:22
Replying to @jhpalmieri:
Well, setting up MPL's config dir based on its version in (as it calls Python before |
comment:23
Replying to @nexttime:
See for example #16044 comment:7 ff. (Note that IIRC |
comment:24
Replying to @jhpalmieri:
On GNU/Linux x86_64, I don't seem to have any environment variables with names containing "MPL", neither in the normal shell nor in
|
comment:25
Replying to @pjbruin:
True. B) $ ./sage --sh -c 'env | grep MPL'; uname -sm
Linux x86_64 |
comment:26
Replying to @nexttime:
It turns out that this is because the following command in
|
comment:27
Replying to @pjbruin:
I'm getting
So apparently |
comment:28
The problem in comment:26 was on 6.2.rc0; with 6.2 on a different system I get
I guess the |
comment:29
Oh, just noticed: # Use a matplotlib config directory specific to Sage and specific to
# the version number of matplotlib, by setting the environment
# variable MPLCONFIGDIR. Note that we can't find the version number by
# importing matplotlib, because that could create matplotlib's standard
# config directory. So we use pkg_resources.
"$SAGE_ROOT/local/bin/python" -c 'import pkg_resources; pkg_resources.get_distribution("matplotlib").version' 2>/dev/null
if [ $? -eq 0 ]; then
MPLVERSION=`"$SAGE_ROOT/local/bin/python" -c 'import pkg_resources; print pkg_resources.get_distribution("matplotlib").version'`
MPLCONFIGDIR="$DOT_SAGE/matplotlib-$MPLVERSION"
export MPLCONFIGDIR
# The directory is created when Sage starts (see sage.misc.misc).
fi
# Add some directories to $LD_LIBRARY_PATH:
# * lib/openmpi is needed for openmpi.
# * lib/R/lib is needed for R in case the Sage install is moved.
# * lib32 and lib64 are needed for GCC, see #12405.
for d in lib/openmpi lib/R/lib lib32 lib64 lib; do
libdir="$SAGE_LOCAL/$d"
# Add only existing directories
if [ -d "$libdir" ]; then
[ -z "$LD_LIBRARY_PATH" ] || LD_LIBRARY_PATH=":${LD_LIBRARY_PATH}"
LD_LIBRARY_PATH="${libdir}$LD_LIBRARY_PATH"
fi
done
export LD_LIBRARY_PATH
|
comment:30
(I meant to say it's done right after we try to call |
comment:31
I created #16305 for this. |
Changed branch from u/jhpalmieri/git-relocate to |
I've compiled sage in
/local/data/krenn/sage-dev/sage-6.1.1
and then moved it to another directory. I am getting the following when testing sage:There are a couple of other files with similar warnings.
CC: @ppurka
Component: misc
Keywords: git, relocate
Author: John Palmieri
Branch/Commit:
782e3f6
Reviewer: Peter Bruin
Issue created by migration from https://trac.sagemath.org/ticket/15901
The text was updated successfully, but these errors were encountered: