Skip to content

Conversation

@topolarity
Copy link
Member

@topolarity topolarity commented Dec 1, 2025

This seems to be an issue at least as far back as 1.10:

$ rm -rf ~/.julia/compiled/*/SuiteSparse/
$ julia +1.10 -q
julia> using SuiteSparse
[ Info: Precompiling SuiteSparse [4607b0f0-06f3-5cda-b6b1-a6196a1729e9]

@topolarity topolarity added backport 1.12 Change should be backported to release-1.12 backport 1.10 Change should be backported to the 1.10 release backport 1.11 Change should be backported to release-1.11 labels Dec 1, 2025
@topolarity
Copy link
Member Author

Unlike 1.10 / 1.11, 1.12 also complains in non-interactive mode:

$ rm -rf ~/.julia/compiled/*/SuiteSparse/
$ julia +1.10 -e "using SuiteSparse"
$ julia +1.12 -e "using SuiteSparse"
Precompiling SuiteSparse finished.
  1 dependency successfully precompiled in 1 seconds

@topolarity topolarity force-pushed the ct/fix-SuiteSparse-pkgimage branch from 6d52982 to 8f5b18b Compare December 1, 2025 22:06
@vtjnash
Copy link
Member

vtjnash commented Dec 2, 2025

That was a known v1.12 bug when we released it, fixed again by #59652 in v1.13

@vtjnash vtjnash merged commit d6f2a7e into JuliaLang:master Dec 2, 2025
9 checks passed
@KristofferC
Copy link
Member

(Which is a user regression because now you look at an empty screen for 5 min wondering if your program is making progress or if things are taking forever precompiling).

KristofferC pushed a commit that referenced this pull request Dec 16, 2025
This seems to be an issue at least as far back as 1.10:
```julia
$ rm -rf ~/.julia/compiled/*/SuiteSparse/
$ julia +1.10 -q
julia> using SuiteSparse
[ Info: Precompiling SuiteSparse [4607b0f0-06f3-5cda-b6b1-a6196a1729e9]
```

(cherry picked from commit d6f2a7e)
KristofferC pushed a commit that referenced this pull request Dec 16, 2025
This seems to be an issue at least as far back as 1.10:
```julia
$ rm -rf ~/.julia/compiled/*/SuiteSparse/
$ julia +1.10 -q
julia> using SuiteSparse
[ Info: Precompiling SuiteSparse [4607b0f0-06f3-5cda-b6b1-a6196a1729e9]
```

(cherry picked from commit d6f2a7e)
@KristofferC KristofferC mentioned this pull request Dec 16, 2025
21 tasks
@KristofferC KristofferC removed the backport 1.12 Change should be backported to release-1.12 label Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 1.10 Change should be backported to the 1.10 release backport 1.11 Change should be backported to release-1.11

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants