tests(docs): clear problematic cache #13941
Conversation
| "private": true, | ||
| "scripts": { | ||
| "install-all": "yarn --cwd auth/ && yarn --cwd integration-test/ && yarn --cwd custom-gatherer-puppeteer/", | ||
| "install-all": "rm -rf /tmp/.junk && rm -f {auth,custom-gatherer-puppeteer,integration-test}/yarn.lock && yarn --cwd auth/ --cache-folder /tmp/.junk && yarn --cwd integration-test/ --cache-folder /tmp/.junk && yarn --cwd custom-gatherer-puppeteer/ --cache-folder /tmp/.junk", |
There was a problem hiding this comment.
Do you mind checking if using npm for the docs stuff works as expected instead? Feels like yarn isn't bringing anything to the relationship in this directory
There was a problem hiding this comment.
Well, at this point I can't recreate the old behavior as it was 1) yarn's cache and 2) I cleared my cache. So we wouldn't be able to detect if this is also an issue in npm.
What are the odds they're using |
|
That is certainly what is happening. I'd consider it a bug, local package zips like that should at least use the mtime or even md5 hash (or just never cache). I'm not motivated to file an issue though... likely it'd be closed as "fixed in yarn 2" lol |
4 participants
We noticed
yarn test-docswas using old builds of lighthouse, which could only be resolved by runningyarn cache clear. This PR avoids the problem by not using the global cache folder, instead this test now uses a throwaway folder. also deletes the lock files.something about using a
.tgzfile as a dependency is caching in an unexpected way 🤷 (just clearing the lock files didn't fix the problem)