-
Notifications
You must be signed in to change notification settings - Fork 57
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
Use scratchspaces rather than .julia/conda #251
Comments
Moving to scratchspaces will probably also fix CI issues where for some reason These issues are not reproducible locally for me, only in CI. E.g. these two lines are necessary in my CI scripts:
Without them, this happens at runtime: I learnt of this workaround from slack where other people were complaining about similar issues. Copied here for archival: Here is the link to the Zygote issue: |
Yes, either:
But note that 2) would require users to opt-in. Doing 3) would probably be a good thing either way. Until then users of Conda.jl are going to have failing because CI caching is becoming more widespread, so it would be wise to consider this an urgent issue |
Just a minor addendum: some of these CI issues I mentioned above are independent of julia-actions/cache (e.g. the ones for buildkite) |
I was directed here with the same issue, namely |
scratchpaces have become the standard place for things like that which are currently stored in
.julia/conda
.Notably CondaPkg.jl uses scratchspaces.
Also, using a custom dir means special handling would be needed for tools like
julia-actions/cache
The text was updated successfully, but these errors were encountered: