I have a private package that I am trying to test. When I run the test suite, it fails, claiming it can’t find CSV: ERROR: LoadError: ArgumentError: Package CSV not found in current path: - Run `import Pkg; Pkg.add("CSV")` to install the CSV package. Stacktrace: [1] require(::Module, ::Symbol) at…

A little more info would be helpful (ideally as a MWE). Do you have, by any chance, a separate test/Project.toml from which CSV is missing? Cf 5. Creating Packages · Pkg.jl Sorry to ask, but is has happened to me before: you are using CSV in runtests.jl?

I don’t have a separate Project.toml in test, but that is a good thing to keep in mind and something I was unaware of. Yes, I am using CSV in runtests.jl. Judging from the tone of your question, this seems to be the problem, but I’m not sure why that’s the case? Thanks for the help.

I had exactly the same problem over the weekend, but when I went now to make a little MWE, I found the problem installing CSV had gone away. The problem only happened when you ran Pkg.test(); just running the tests directly from the command line worked fine. Could there have been some corruption pro…

actually, I still get the error in Travis: Travis CI - Test and Deploy with Confidence Travis CI enables your team to test and ship your apps with confidence. Easily sync your projects with Travis CI and you'll be testing your code in minutes. [...] ERROR: …

What I had in mind was that you might be calling a CSV function in the tests without using CSV in runtests.jl, but that doesn’t seem to be the problem. Then I’m afraid it’s hard to figure out the problem without a MWE.

Maybe, the same solution works here: CSV Parsers dependency problem [image] CSV Parsers dependency problem I think the issue is that the previous CSV.jl release probably has a dependency version like “Parsers >= 0.2” or something, and then when Parsers.jl made a breaking release to 0.3.0 , it br…

It might be easier than that: if you don’t have a separate environment for the tests, include all the packages used in runtests.jl in the corresponding target of the package’s Project.toml, for instance: [targets] test = ["Test", "CSV", "MoltenSaltThermodynamics"]

Thanks everyone for the help! In the end I was able to solve the problem by creating a specific environment for testing as described in the link that @hendri54 posted. That seems to be the best way of going about this. I didn’t know that Julia had added that capability, but it shows me that I should…

Testing private package fails based on dependency

General Usage

Tero_Frondelius June 18, 2020, 12:08pm 7

Maybe, the same solution works here: CSV Parsers dependency problem

Topic		Replies	Views
Packaging: why can't Julia find Test in Travis? General Usage question , package	2	684	June 23, 2020
Confused by pkg> test behavior Package Management pkg	2	615	March 4, 2020
[pkg test] Error on explicit mention of tested package in Project.toml General Usage package , testing	4	756	November 7, 2021
Add Test as a dependency of project General Usage testing , pkg	6	845	November 9, 2022
Pkg.test does not recognize package dependencies General Usage	3	571	October 19, 2018

Testing private package fails based on dependency

Related topics