-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Cache generation for stdlib on read-only FS fails #50206
Comments
How much of the file system is read only? Where could these be saved? |
From the log:
The first entry of the depots list is supposed to be writable, it looks like this isn't the case in PkgEval? Edit: nevermind, it fails to write in |
Yeah. It could save the pidfile in the depot, but the issue is the cachefile directory slug isn't known ahead of spawning off the child to do the precomp, which is why it's specific to the sourcepath currently. I guess the lock could be more general for a package (and Julia version) and save as |
Yeah we should put the PID lock into the same location as the output file. We could also sink the lock closer to where we determine the slug |
The latter would mean you couldn't avoid spawning a julia process. What about |
Why? The slug is determined by the parent.
Maybe simply |
AFAICT that's not true. The full path isn't known by the parent because of things like preferences etc |
FWIW, double |
Yeah... Only due to preferences. Line 2316 in 9501540
|
Still seems to happen on https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_date/2023-06/19/report.html, which includes f555b4b
or https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_date/2023-06/19/AEMS.against.log
|
It can't have the new commit, I changed from a ".pidlock" to ".pidfile" extension for one thing |
My mistake, I was looking at the |
Seen during https://s3.amazonaws.com/julialang-reports/nanosoldier/pkgeval/by_hash/d9a5a29_vs_65523e4/MultiStateSystems.primary.log
cc: @IanButterworth
The text was updated successfully, but these errors were encountered: