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

Configure restore-keys for puppeteer cache in ci:test #975

Merged
merged 1 commit into from
May 20, 2024

Conversation

make-github-pseudonymous-again
Copy link
Contributor

This fixes #865 for good.

Since meteor-actions/install now can skip the installation of cached packages using restore keys, it can happen that node_modules/puppeteer is restored from cache while its chromium download is not.

With this commit, we ensure that the weakest restore key for chromium is at least as weak as the weakest restore key for node_modules/puppeteer.

Maybe an alternative would be to instruct puppeteer to install chromium under node_modules? But for now, this is good enough.

…flow.

This fixes #865 for good.

Since `meteor-actions/install` now can skip the installation of cached
packages using restore keys, it can happen that `node_modules/puppeteer`
is restored from cache while its `chromium` download is not.

With this commit, we ensure that the weakest restore key for `chromium`
is at least as weak as the weakest restore key for
`node_modules/puppeteer`.

Maybe an alternative would be to instruct `puppeteer` to install
chromium under `node_modules`? But for now, this is good enough.
@make-github-pseudonymous-again make-github-pseudonymous-again added ci This issue is about continuous integration dx This is about developer experience labels May 20, 2024
@make-github-pseudonymous-again make-github-pseudonymous-again marked this pull request as ready for review May 20, 2024 19:53
Copy link

codecov bot commented May 20, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.86%. Comparing base (6308ea8) to head (30a1651).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #975      +/-   ##
==========================================
- Coverage   65.88%   65.86%   -0.03%     
==========================================
  Files         715      715              
  Lines        9893     9893              
  Branches     1346     1346              
==========================================
- Hits         6518     6516       -2     
- Misses       2917     2919       +2     
  Partials      458      458              
Flag Coverage Δ
client 46.23% <ø> (-0.03%) ⬇️
server 61.87% <ø> (ø)
test 71.97% <ø> (ø)
test-app 53.70% <ø> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Merged via the queue into main with commit d539968 May 20, 2024
33 checks passed
@make-github-pseudonymous-again make-github-pseudonymous-again deleted the ci-fix-puppeteer-cache-1 branch May 20, 2024 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci This issue is about continuous integration dx This is about developer experience
Projects
Development

Successfully merging this pull request may close these issues.

Fix sporadic client tests timeout on Github Actions
1 participant