# Test pulling down older versions of packages in Extras than it should

**URL:** https://discourse.julialang.org/t/test-pulling-down-older-versions-of-packages-in-extras-than-it-should/105245
**Category:** General Usage
**Tags:** testing, package-manager
**Created:** [October 20, 2023, 4:34pm UTC](https://discourse.julialang.org/t/test-pulling-down-older-versions-of-packages-in-extras-than-it-should/105245 "2023-10-20T16:34:55Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Allan\_Baker](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/allan_baker/32/42645_2.png) [@Allan\_Baker](https://discourse.julialang.org/u/Allan_Baker)
#### Post date: [October 20, 2023, 4:34pm UTC](https://discourse.julialang.org/t/test-pulling-down-older-versions-of-packages-in-extras-than-it-should/105245/1 "2023-10-20T16:34:55Z")

</div>

For some reason this stopped working after I did the last `]update`.  
I have several plotting extensions for some home-grown packages I’m referencing. This all worked fine, but now when I run the package test from the Project’s active directory, it fails. `] test`

If I go to an Example directory where I have added all the weak dependencies (so I can more easily debug and try stuff on the command line) and run the `]test ProjectName` from there, it pulls in a later version of the extension and it passes.

I used to have the Extras in their own “test/Project.toml” and the test run out of the ProjectName seemed to stop referencing it.

Is there a Cache I need to kill somewhere, because… the WSL ubuntu linux julia version, pointing to the same directory space, passed it’s test with the later versions where Window’s version failed.

How do I see what is messing up when “test” is making up it’s own Manifests? How do I find why things are being limited just for it?