Open ctkelley opened 9 months ago
You may need to remove ~/.Julia/environments/v1.11
and try again. I think this should fix it. Perhaps removing the manifest and resolving packages may be enough
It should work around it yes, but it is still unclear to me why Pkg would have to recompile at all in this situation.
You may need to remove ~/.Julia/environments/v1.11 and try again. I think this should fix it. Perhaps removing the manifest and resolving packages may be enough
That does not work for me; just import Pkg
in the default environment also triggers this for me.
EDIT: I had not removed the environment completely; Libgit2 was still in there. Seems like that indeed was the cause.
This seems to be a bigger issue - I get the same kind of problem when I try to run the tests of one of my packages on nightly. The package has a Project.toml
.
This seems to be a bigger issue - I get the same kind of problem when I try to run the tests of one of my packages on nightly. The package has a Project.toml.
Link to log?
Working on a bisect, I'll link a gist when I'm done. I'm not sure if it happens in CI too, I've only noticed it when manually running ]test
in the REPL so far.
The bisect is 99% when Pkg got moved out of the sysimage (and is in combination with https://github.com/JuliaLang/julia/pull/51294).
The specific issue I'm seeing is bisected to https://github.com/JuliaLang/julia/pull/51399
Gist for the log I'm seeing is here. The package in question is this, but I suspect it doesn't matter; likely any testsuite based on Project.toml will do, when triggered from the REPL.
Duplicate of https://github.com/JuliaLang/julia/issues/51452?
After applying the latest backport for version 1.10 https://github.com/JuliaLang/julia/pull/50971 the same problem occurs when building julia. Removing .julia/environments/v1.10/Manifest.toml
is the solution.
Just tried
Version 1.11.0-DEV.590
on an Intel Mac (Sonoma) and all is well after I delete
.julia/environments/v1.11/Manifest.toml
Will try on an M2 Mac later today.
Just did it and it works. Look like this problem is fixed (at least for me).
I just tried the latest nightly and got this. Tried to
import Pkg
and got similar results.