TestEnv.jl icon indicating copy to clipboard operation
TestEnv.jl copied to clipboard

Warning when activating test environment in 1.8

Open ufechner7 opened this issue 3 years ago • 3 comments

On Julia 1.8-beta3, I always get the following warning:

julia> using TestEnv; TestEnv.activate()
┌ Warning: The project dependencies or compat requirements have changed since the manifest was last resolved.
│ It is recommended to `Pkg.resolve()` or consider `Pkg.update()` if necessary.
└ @ Pkg.API /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.8/Pkg/src/API.jl:1527
"/tmp/jl_sHrfez/Project.toml"

Can this be fixed in in TestEnv.jl ?

ufechner7 avatar Apr 10 '22 10:04 ufechner7

Some digging will need to be done. we call instantiate here: https://github.com/JuliaTesting/TestEnv.jl/blob/1f0f6eb302f7661064226d9722f2fc8dced1825a/src/common.jl#L22 which errors because of the code here: https://github.com/JuliaLang/Pkg.jl/blob/16c3d6a7ad0075a56c8da300811b0e5249ab9e39/src/API.jl#L1526-L1529 which is calling https://github.com/JuliaLang/Pkg.jl/blob/16c3d6a7ad0075a56c8da300811b0e5249ab9e39/src/Operations.jl#L2184-L2193

oxinabox avatar May 10 '22 17:05 oxinabox

This should only happen if the Project.toml has been changed after the last resolve. (It's supposed to flag that, so you don't end up with a manifest that isn't a valid resolve of the project)

Does that happen in TestEnv?

IanButterworth avatar May 24 '22 15:05 IanButterworth

It effectively generates a new Project.toml (possibly literally, I would need to check)

The code in the release-1.8 is basically taken direct from Pkg v1.7's source.

oxinabox avatar May 25 '22 10:05 oxinabox