Skip to content

ci(NODE-6501): use latest node in spec benchmarks #4314

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

Merged
merged 6 commits into from
Nov 5, 2024
Merged

ci(NODE-6501): use latest node in spec benchmarks #4314

merged 6 commits into from
Nov 5, 2024

Conversation

baileympearson
Copy link
Contributor

@baileympearson baileympearson commented Nov 5, 2024

Description

What is changing?

We use latest LTS (v22.11.0) for performance testing. Also, the runner now has a max number of executions set to 10 million, to prevent OOM errors on the returnDocument test.

Is there new documentation needed for these changes?

What is the motivation for this change?

Release Highlight

Fill in title or leave empty for no highlight

Double check the following

  • Ran npm run check:lint script
  • Self-review completed using the steps outlined here
  • PR title follows the correct format: type(NODE-xxxx)[!]: description
    • Example: feat(NODE-1234)!: rewriting everything in coffeescript
  • Changes are covered by tests
  • New TODOs have a related JIRA ticket

@baileympearson baileympearson marked this pull request as ready for review November 5, 2024 17:27
@nbbeeken nbbeeken self-assigned this Nov 5, 2024
@nbbeeken nbbeeken added the Primary Review In Review with primary reviewer, not yet ready for team's eyes label Nov 5, 2024
@nbbeeken nbbeeken merged commit dc3fe95 into main Nov 5, 2024
26 of 27 checks passed
@nbbeeken nbbeeken deleted the NODE-6501 branch November 5, 2024 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Primary Review In Review with primary reviewer, not yet ready for team's eyes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants