Closed eldond closed 1 year ago
Most probably this is because your SOLPS2IMAS package is out of date locally. I remember seeing an issue like this before. For me it got fixed after https://github.com/ProjectTorreyPines/SOLPS2IMAS.jl/commit/4ca3759c8c10d43b385c7506d837a27dbd0d16a7
Please pull SOLPS2IMAS dev branch. If the problem persists, try doing following:
cd SD4SOLPS.jl # Your SD4SOLPS.jl repo path
julia --project=./
julia>]
(SD4SOLPS) pkg > rm SOLPS2IMAS.jl
(SD4SOLPS) pkg > add "git@github.com:ProjectTorreyPines/SOLPS2IMAS.jl.git"#dev
(SD4SOLPS) pkg > instantiate
Then try running the test again as:
cd SD4SOLPS.jl # Your SD4SOLPS.jl repo path
julia --project=./ test/runtests.jl
I can confirm that all tests are passing on current dev branch on my machine where latest dev branches have been pulled. One other way of keeping your local project manifest up to date with changing dependencies is to add the packages using dev with local addressing. For example, I have following tree structure:
(base) gupta@F-CJXNMY7L7 ProjectTorreyPines % tree -L 1
.
├── FUSEDivertor.jl
├── GGDUtils.jl
├── OMAS.jl
├── SD4SOLPS.jl
├── SOLPS2IMAS.jl
├── SOLPSTestSamples
├── Scratch
└── SynthDiag.jl
Then for ensuring that local packages with latest updates are used, I add them as:
cd SD4SOLPS.jl
julia --project=./
julia>]
(SD4SOLPS) pkg > dev ../OMAS.jl
(SD4SOLPS) pkg > dev ../SOLPS2IMAS.jl
(SD4SOLPS) pkg > dev ../GGDUtils.jl
You might have to remove some of these in order to add them again with dev tag. This might not be the best way to do this, but it has been working out fine with me. Note that the hash in Project.toml does not change even when we use local packages. Once we release the packages in future, people should be able to use Project.toml directly.
Let me know if you still face this error.
Thanks. It was out of date dependencies.
I'm going to try using mr
to avoid this next time.
GGDUtils on dev at dea75179f168c1a75a6265d14c18967a0c83e1d5 SD4SOLPS on dev at 31dafe5936b038d372ba2c3e36b8163cc5db7c8b