# Can't test package: "in manifest but not in project"

**URL:** <https://discourse.julialang.org/t/cant-test-package-in-manifest-but-not-in-project/32663>\
**Category:** General Usage\
**Tags:** pkg\
**Created:** [December 24, 2019, 4:55pm UTC](https://discourse.julialang.org/t/cant-test-package-in-manifest-but-not-in-project/32663 "2019-12-24T16:55:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yha](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/yha/32/3502_2.png) [@yha](https://discourse.julialang.org/u/yha)\
**Post date:** [December 24, 2019, 4:55pm UTC](https://discourse.julialang.org/t/cant-test-package-in-manifest-but-not-in-project/32663/1 "2019-12-24T16:55:53Z")

</div>

I have the registered `CircularArrays` package `dev`ed, but I can’t test it, and can’t make sense of the error message

```julia
(v1.3) pkg> status CircularArrays
    Status `C:\Users\sternlab\.julia\environments\v1.3\Project.toml`
  [dcaa3502] CircularArrays v0.1.0 [`C:\Users\sternlab\.julia\dev\CircularArrays`]
  [6fe1bfb0] OffsetArrays v0.11.4

(v1.3) pkg> test CircularArrays
ERROR: The following package names could not be resolved:
 * CircularArrays (7a955b69-7140-5f4e-a0ed-f168c5e2e749 or dcaa3502-af75-11e8-34c7-6b8fb8855653 in manifest but not in project)
Please specify by known `name=uuid`.

```

The `Manifest.TOML` file for the default environment lists the package twice:

```julia
[[CircularArrays]]
deps = ["OffsetArrays"]
path = "C:\\Users\\sternlab\\.julia\\dev\\CircularArrays"
uuid = "dcaa3502-af75-11e8-34c7-6b8fb8855653"
version = "0.1.0"
[[CircularArrays]]
deps = ["Test"]
git-tree-sha1 = "310214c08082c8a408f8f7839da0418cef60c117"
uuid = "7a955b69-7140-5f4e-a0ed-f168c5e2e749"
version = "0.1.0"

```

This doesn’t change after `]remove CircularArrays; dev CircularArrays; resolve`

Edit: using `Pkg.test` instead of `]test` seems to work, but I still don’t understand what is going on.

---

<div class="post-metadata">

**Author:** ![00vareladavid](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/00vareladavid/32/23521_2.png) [@00vareladavid](https://discourse.julialang.org/u/00vareladavid)\
**Post date:** [December 25, 2019, 5:57am UTC](https://discourse.julialang.org/t/cant-test-package-in-manifest-but-not-in-project/32663/2 "2019-12-25T05:57:45Z")

</div>

This seems to be a Pkg bug stemming from the fact that you have two dependencies with the same name but different UUID.

It doesn’t occur on master and there is a pending PR to prevent any regressions: [https://github.com/JuliaLang/Pkg.jl/pull/1563](https://github.com/JuliaLang/Pkg.jl/pull/1563).

As for your current situation, you can always `activate` the dependency directly then call `test` with no arguments.

---

<div class="post-metadata">

**Author:** ![yha](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/yha/32/3502_2.png) [@yha](https://discourse.julialang.org/u/yha)\
**Post date:** [December 25, 2019, 4:53pm UTC](https://discourse.julialang.org/t/cant-test-package-in-manifest-but-not-in-project/32663/3 "2019-12-25T16:53:28Z")

</div>

> [@00vareladavid](#):
>
> This seems to be a Pkg bug stemming from the fact that you have two dependencies with the same name but different UUID.

I don’t really have two different dependencies. I tracked down the two UUIDs: one comes from the package’s Project.TOML: [https://github.com/Vexatos/CircularArrays.jl/blob/master/Project.toml](https://github.com/Vexatos/CircularArrays.jl/blob/master/Project.toml), and the other from the Package.TOML registering _the same_ package in the General registry.  
Does this mean there’s an error in the registry?

---

<div class="post-metadata">

**Author:** ![00vareladavid](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/00vareladavid/32/23521_2.png) [@00vareladavid](https://discourse.julialang.org/u/00vareladavid)\
**Post date:** [December 25, 2019, 7:46pm UTC](https://discourse.julialang.org/t/cant-test-package-in-manifest-but-not-in-project/32663/4 "2019-12-25T19:46:37Z")

</div>

Yeah there is a discrepancy. Probably easier to change the UUID in the original repo though