Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CircleCI: Fix nodejs cache poisoning #7726

Closed
wants to merge 1 commit into from

Conversation

roidelapluie
Copy link
Member

@roidelapluie roidelapluie commented Aug 2, 2020

This wrong cache makes tests fail

Signed-off-by: Julien Pivotto roidelapluie@inuits.eu

This wrong cache makes react tests fail

Signed-off-by: Julien Pivotto <roidelapluie@inuits.eu>
@@ -28,7 +28,6 @@ jobs:
- restore_cache:
keys:
- v1-npm-deps-{{ checksum "web/ui/react-app/yarn.lock" }}
- v1-npm-deps-
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, in #6181 (comment) @simonpasquier explicitly confirmed this line should be there, but I guess this can cause problems when we actually depend on slightly different packages.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I see is tests fail:

o cache is found for key: v1-npm-deps-4FzFT0c3EEonV6JVriNMN0rzzFiM6RAWpqgTIHHJews=
Found a cache from build 36397 at v1-npm-deps-
Size: 56 MiB
Cached paths:
  * /home/circleci/project/web/ui/react-app/node_modules

Downloading cache archive...
Validating cache...

Unarchiving cache...

But 36397 is my update deps PR.

I don't know why the cache was not found (https://app.circleci.com/pipelines/github/prometheus/prometheus/8367/workflows/873e94be-223e-4fae-9daf-9f20348d10f1/jobs/36573) but I think we would better start fresh anyway.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Especially since yarn does not seem to see that the dependencies are wrong.

@juliusv
Copy link
Member

juliusv commented Aug 2, 2020

👍 I think, would be good to get confirmation by @simonpasquier

@roidelapluie
Copy link
Member Author

#7727 might be a better fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants