Changed the ModiaMath travis.yml file to use Julia 0.7. Now, travis cl fails with the message : $ julia --check-bounds=yes --color=yes -e "if VERSION < v\"0.7.0-DEV.5183\"; Pkg.test(\"${JL_PKG}\", coverage=true); else using Pkg; Pkg.test(coverage=true); end" Testing ModiaMath Resolving package v…

The fact that Modia depends on StaticArrays does not mean that we can load StaticArrays in the REPL. For that, StaticArrays has to be explicitly added by the user.

I finally found a good solution (could be a template for other packages as well): The source of the problem is that (a) there are external Julia “scripts” under ModiaMath/examples and ModiaMath/test that use package ModiaMath to demonstrate/test its features and (b) these “scripts” import other pac…

Tom Short wrote here : The code from 479cec8 seems like a kludgy solution. I’m not sure what’s the best approach. Maybe it points to the need for better Base tooling. How about including an examples/Project.toml with those dependencies? The user would have to activate that to run the code. i hop…

Why can’t you just Pkg.add what you need in the example scripts? Or simply put it in the documentation: To run the following example you need to install Modia, LinearAlgebra and StaticArrays.

One problem with including calls to Pkg.add() is that it changes the current environment. The user may not want that. Another option is to Pkg.activate("path/to/examples") and include a Project.toml there like you did for Literate.jl/docs.

I just don’t understand why you would try to hide the dependencies like this. Presumably the examples are there for users to study them, and to be able to modify/extend/write their own programs, and if the examples generally uses e.g. StaticArrays then why not be open with that such that users under…

I don’t think they’ll be hidden in that the using Whatever will still be there. I’m also good with the idea of adding documentation. The Pkg.add() part seemed klunky.

Right, but the commit linked above, where e.g. using StaticArrays was replaced with using Modia.StaticArrays is a bit weird, it looks more like an internal module than the actual StaticArrays package.

Agreed. That’s the reason for reaching out for other ideas.

I think that documenting what packages you need to run the examples, and also provide a examples/Project.toml with the required deps that users can instantiate is a good way.

Travis CI fails for Julia v0.7 since Test package missing

Tooling

fredrikekre September 14, 2018, 6:21am 27

You can think of Project.toml’s [deps] section as the old REQUIRE file.

Topic		Replies	Views
Error using package in local environment General Usage testing , configuration	17	1464	July 17, 2024
Pkg.add() refuses to use the required version General Usage	9	2516	August 14, 2018
Packaging: why can't Julia find Test in Travis? General Usage question , package	2	639	June 23, 2020
Errors when testing unregistered custom package (because of non-ASCII characters, it seems) Package Management testing , strings , pkg	24	2726	June 1, 2020
Installing dependencies for separate Project.toml during package development/testing Package Management question , pkg	3	1480	October 27, 2021

Travis CI fails for Julia v0.7 since Test package missing

Related topics