Happy new year,
which I so far have spent with moving my tests from Travis to GitHub Actions. After finally getting it somewhere, I ran into a problem which I already had on Travis.
When using a unregistered package, in my case MKL.jl, the documentation suggest running
- julia --project --color=yes --check-bounds=yes -e 'using Pkg; Pkg.develop(PackageSpec(path="/home/travis/build/path_to_private_Dependency")); Pkg.instantiate()'
where I run
- julia --project --color=yes --check-bounds=yes -e 'using Pkg; Pkg.add(PackageSpec(url="https://github.com/JuliaComputing/MKL.jl"));'
which takes >10 min usually, which by itself is fine.
However, the problem is that the default build command for the tested package itself builds MKL.jl once more, again taking 10 min.
I tried to address this by only prompting for the package itself
- julia --color=yes -e "if VERSION < v\"0.7.0-DEV.5183\"; Pkg.clone(pwd()); Pkg.build(\"IntelVectorMath\"); else using Pkg; if VERSION >= v\"1.1.0-rc1\"; Pkg.build(\"IntelVectorMath\"; verbose=true); else Pkg.build(\"IntelVectorMath\"); end; end"
but MKL still gets rebuild.
I expect that this specific problem will soon be solved as MKL.jl nears proper registration. But in principle I think there should be a way to avoid something like this.
Pkg.add(..., build=false) or so? Or maybe there is a trick that I haven’t found yet that would help here.
Any input would be appreciated.