Precompiling VectorizationBase errors in Ubuntu, julia 1.7.2

[ismedina]

Hi! I get a precompilation error when importing VectorizationBase. Originally I got this error when trying to install DifferentialEquations.jl, but I reproduce the error just adding VectorizationBase. I can reproduce it with julia 1.7.2 or 1.6.5 in Ubuntu, Below the stacktrace (for julia 1.7.2, for 1.6.5 I get the same):

julia> using VectorizationBase
[ Info: Precompiling VectorizationBase [3d5dd08c-fd9d-11e8-17fa-ed2836048c2f]
ERROR: LoadError: UndefVarError: num_cache_levels not defined
Stacktrace:
 [1] include
   @ ./Base.jl:418 [inlined]
 [2] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt64}}, source::Nothing)
   @ Base ./loading.jl:1318
 [3] top-level scope
   @ none:1
 [4] eval
   @ ./boot.jl:373 [inlined]
 [5] eval(x::Expr)
   @ Base.MainInclude ./client.jl:453
 [6] top-level scope
   @ none:1
in expression starting at /home/ismael/.julia/packages/VectorizationBase/yDGcX/src/VectorizationBase.jl:1
ERROR: Failed to precompile VectorizationBase [3d5dd08c-fd9d-11e8-17fa-ed2836048c2f] to /home/ismael/.julia/compiled/v1.7/VectorizationBase/jl_voXyGg.
Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:33
 [2] compilecache(pkg::Base.PkgId, path::String, internal_stderr::IO, internal_stdout::IO, ignore_loaded_modules::Bool)
   @ Base ./loading.jl:1466
 [3] compilecache(pkg::Base.PkgId, path::String)
   @ Base ./loading.jl:1410
 [4] _require(pkg::Base.PkgId)
   @ Base ./loading.jl:1120
 [5] require(uuidkey::Base.PkgId)
   @ Base ./loading.jl:1013
 [6] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:997

Any ideas? Thanks in advance!

[lcontento]

It looks to be caused by significant changes in the CPUSummary package. I can make it load by reverting to an older version pkg> pin [email protected]

[chriselrod]

This should be fixed soon JuliaRegistries/General#55825

[ismedina]

Thank you both for the very very fast reply! @lcontento's answer worked for me, in the meantime until it is fixed in general. Should I close this?

[chriselrod]

Thank you both for the very very fast reply! @lcontento's answer worked for me, in the meantime until it is fixed in general. Should I close this?

I can close it once I release a new version of VB that excludes the problematic CPUSummary versions.

[chriselrod]

Please let me know if you run into any more problems!