tests(legacy-javascript): pin to specific versions of core-js #12265
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adamraine
approved these changes
Mar 18, 2021
| for (const coreJsVersion of ['2.6.12', '3.9.1']) { | ||
| const major = coreJsVersion.split('.')[0]; | ||
| removeCoreJs(); | ||
| installCoreJs(coreJsVersion); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
These test results were changing whenever core-js released a new version. This was overlooked because we don't use yarn.lock to pin these version, but instead manually install the package (since we switch between core-js 2 and 3). Instead, specify what version to install in
run.js.I noticed this here: https://github.com/GoogleChrome/lighthouse/pull/12199/checks?check_run_id=2134061233