During update of julia 1.6.0, while precompiling the project, I get indication of (previous) failed module precompilation.
(@v1.6) pkg> up
Updating registry at `C:\Users\davidj\.julia\registries\General`
Updating git-repo `https://github.com/JuliaRegistries/General.git`
Installed Tokenize ─ v0.5.10
No Changes to `C:\Users\davidj\.julia\environments\v1.6\Project.toml`
[0796e94c] ↑ Tokenize v0.5.8 ⇒ v0.5.10
Progress [========================================>] 7/7
6 dependencies successfully precompiled in 44 seconds (247 already precompiled, 1 skipped during auto due to previous er
Is there a way (other than doing
using on each module) to know which module failed/was skipped ? Or may be, a way to have the precompilation status of each module (may be with a mark in the “]status” command?) ?
Almost for sure this is the issue:
GR_jll seems to be the only Julia package with some problems when running on 1.6.0 RC1
Is there any solution for this kind of errors?
The auto-precompilation that happens after
pkg> add/up etc. tries to be quieter about package errors because during Pkg operations you may only care about a subset of packages in your environment.
For that reason auto-precompilation does two things:
- Only warns that packages have errored, and doesn’t show the full stack trace. (That warning comes with guidance to run
precompile manually, or load the package)
- Remembers if packages have errored in previous Pkg precompile attempts and skips them, just showing the
1 skipped during auto due to previous errors type of message.
pkg> precompile retries precompilation on all packages, and will show the full error messages.
And of course packages can just be loaded via
using/import to hit the classical precompile process and error handling.
]precompile is the answer to my question.