-
Notifications
You must be signed in to change notification settings - Fork 459
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
fix: lower cache usage by reusing more of the yarn caches #3162
Conversation
38d58b2
to
e13b3ac
Compare
e13b3ac
to
f18e977
Compare
f18e977
to
b077535
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❌ (Can't request changes, as it's my PR 🙄)
The rebase actually removed some intended part, as can be seen in this old commit of mine: f18e977#diff-82454b2fc887e9985b9348b8f3bca03d2f839645a4c3ba1f3f850014d7da5c8bR118
Co-authored-by: Ansgar Mertens <[email protected]>
Co-authored-by: Ansgar Mertens <[email protected]>
I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Github showed ~500MB per yarn cache, so let's not use one distinct cache per integration test or unit test since that definitely causes evictions at 10GB total maximum for caches 😅