-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Upgrade node to 18.20 #40661
Upgrade node to 18.20 #40661
Conversation
Codenotify: Notifying subscribers in CODENOTIFY files for diff cc1f9f0...5b94085.
|
This reverts commit 8f4b39e.
@@ -80,7 +80,7 @@ describe("ChartSettingLinkUrlInput", () => { | |||
const options = await getOptions(); | |||
|
|||
userEvent.click(options[1]); | |||
input.blur(); | |||
userEvent.tab(); |
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.
will be reverted before merge. I used it only for triggering unit tests
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.
@uladzimirdev Should we add .nvmrc
to frontend_sources
?
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.
Awesome! 💯
|
@uladzimirdev Did you forget to add a milestone to the issue for this PR? When and where should I add a milestone? |
* Upgrade node to 18.20 * Trigger CI * Try 20 again * Revert "Try 20 again" This reverts commit 8f4b39e. * Revert change * Add nvmrc to the frontend_sources list
* Upgrade node to 18.20 * Trigger CI * Try 20 again * Revert "Try 20 again" This reverts commit 8f4b39e. * Revert change * Add nvmrc to the frontend_sources list
Description
The node.js fix that affects jest performance was backported to 18.20, so we want to upgrade and get benefits from the tests speed
nodejs/node#51004
The fix is important as after node 16.* some regression related to reading and keeping files in memory was introduced in the node core and every next version of node made jest performance worse.
Related jest issue jestjs/jest#11956
Local test results running
yarn jest --maxWorkers=4 --silent
As per CI time - it can vary, but we can check trunk stats after 1–2 weeks