Configure restore-keys
for puppeteer cache in ci:test
#975
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #865 for good.
Since
meteor-actions/install
now can skip the installation of cached packages using restore keys, it can happen thatnode_modules/puppeteer
is restored from cache while itschromium
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 fornode_modules/puppeteer
.Maybe an alternative would be to instruct
puppeteer
to install chromium undernode_modules
? But for now, this is good enough.