Skip to content
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

Julia 1.11.1 precompilations and freeze with -O3 #56207

Closed
ancapdev opened this issue Oct 17, 2024 · 4 comments · Fixed by #56214
Closed

Julia 1.11.1 precompilations and freeze with -O3 #56207

ancapdev opened this issue Oct 17, 2024 · 4 comments · Fixed by #56214
Labels
regression 1.11 Regression in the 1.11 release

Comments

@ancapdev
Copy link
Contributor

Installed julia 1.11.1 with juliaup. Launching with no arguments worked as expected. Launching with -O3 caused some core packages to precompile, I'm guessing the -O3 binary code is missing from the system image (I can't remember this being an issue on older versions). Upon entering pkg mode, further packages start precompiling, but no progress is made. Full output:

(unable to copy from the terminal while it's updating, so attached as screenshot)

Image

ctrl+c doesn't seem to kill this process either, I had to manually kill it. Starting Julia fresh again with -O3 and it freezes the same way when entering pkg mode.

@giordano
Copy link
Contributor

Does this happen with v1.11.0? Is this related to #56054?

@ancapdev
Copy link
Contributor Author

It could be related, but I haven't experienced this issue on v1.11.0 myself.

@giordano giordano added bisect wanted regression 1.11 Regression in the 1.11 release labels Oct 17, 2024
@giordano
Copy link
Contributor

A git bisect would be helpful then.

@ancapdev
Copy link
Contributor Author

I've not had time to bisect, but I've found that if I force precompilation of Pkg by using Pkg first, then everything works fine, including subsequent sessions. It would seem to be the same issue as #56054 potentially then, and I think it may have been masked in my 1.11.0 install by a startup.jl file I had which used Pkg and caused the precompilation there. In trying to diagnose an unrelated issue between first installing 1.11.0 and now installing 1.11.1 I had disabled my startup.jl script. I'm guessing my 1.11.0 install was working because the compile cache had already been populated.

vtjnash added a commit that referenced this issue Oct 17, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs.

Fixes #56207
Fixes #56054
Fixes #56206
vtjnash added a commit that referenced this issue Oct 17, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs.

Fixes #56207
Fixes #56054
Fixes #56206
vtjnash added a commit that referenced this issue Oct 17, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs.

Fixes #56207
Fixes #56054
Fixes #56206
vtjnash added a commit that referenced this issue Oct 17, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs. The printing
also failed to meaningfully represent the settings for the same reasons.

Fixes #56207
Fixes #56054
Fixes #56206
vtjnash added a commit that referenced this issue Oct 17, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs. The printing
also failed to meaningfully represent the settings for the same reasons.

Also fixes a concurrency bug in loading.jl tests that was failing.

Fixes #56207
Fixes #56054
Fixes #56206
vtjnash added a commit that referenced this issue Oct 18, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs.

Fixes #56207
Fixes #56054
Fixes #56206
KristofferC pushed a commit that referenced this issue Oct 21, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs.

Fixes #56207
Fixes #56054
Fixes #56206

(cherry picked from commit 82b1506)
KristofferC pushed a commit that referenced this issue Oct 21, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs.

Fixes #56207
Fixes #56054
Fixes #56206
maleadt pushed a commit that referenced this issue Oct 21, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs.

Fixes #56207
Fixes #56054
Fixes #56206

(cherry picked from commit 82b1506)
KristofferC pushed a commit that referenced this issue Oct 24, 2024
CacheFlags could get set, but were never propagated to the target
process, so the result would be unusable. Additionally, the debug and
optimization levels were not synchronized with the sysimg, causing a
regression in pkgimage usability after moving out stdlibs.

Fixes #56207
Fixes #56054
Fixes #56206

(cherry picked from commit 82b1506)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
regression 1.11 Regression in the 1.11 release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants