Skip to content

lib: put node:bench behind an --experimental-bench flag - #65920

Open
jasnell wants to merge 2 commits into
nodejs:mainfrom
jasnell:jasnell/node-bench-flag
Open

lib: put node:bench behind an --experimental-bench flag#65920
jasnell wants to merge 2 commits into
nodejs:mainfrom
jasnell:jasnell/node-bench-flag

Conversation

@jasnell

@jasnell jasnell commented Sep 8, 2026

Copy link
Copy Markdown
Member

Stacks after #65919 .. the first commit here is from that

The second commit puts the experimental node:bench properly behind the --experimental-bench flag, which I completely missed on the initial landing.

@jasnell
jasnell requested review from ljharb and mcollina September 8, 2026 21:22
@jasnell jasnell added benchmark Issues and PRs related to Node.js benchmarks and benchmarking infrastructure. experimental Issues and PRs related to experimental features. labels Sep 8, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/config
  • @nodejs/loaders
  • @nodejs/performance
  • @nodejs/startup

@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. lib / src Issues and PRs involving general changes in the lib/ or src/ directories. needs-ci PRs that need a full CI run. labels Sep 8, 2026
@jasnell
jasnell force-pushed the jasnell/node-bench-flag branch from 7575fec to 79fa17e Compare September 8, 2026 21:32
@nodejs-github-bot

This comment was marked as outdated.

I believe the test-bench-cli flakes were just because the
one file was doing too much and on some architectures was
taking too long to complete. This splits up the file.
At the very least, if there's still a flake in here, the
smaller, more focused files should help narrow it down

Signed-off-by: James M Snell <jasnell@gmail.com>
Signed-off-by: James M Snell <jasnell@gmail.com>
Assisted-by: Opencode
@jasnell
jasnell force-pushed the jasnell/node-bench-flag branch from 79fa17e to b3204fc Compare September 9, 2026 01:25
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@meixg meixg added the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Sep 9, 2026
@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Sep 9, 2026
@nodejs-github-bot

This comment was marked as duplicate.

@aduh95

aduh95 commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

@meixg why do you add request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. on PR that already have a running CI? It puts unneeded load on an already overloaded CI, please stop

@meixg

meixg commented Sep 9, 2026

Copy link
Copy Markdown
Member

@meixg why do you add request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. on PR that already have a running CI? It puts unneeded load on an already overloaded CI, please stop

Sorry about that, I didn't check carefully, My bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

benchmark Issues and PRs related to Node.js benchmarks and benchmarking infrastructure. c++ Issues and PRs that require attention from people who are familiar with C++. experimental Issues and PRs related to experimental features. lib / src Issues and PRs involving general changes in the lib/ or src/ directories. needs-ci PRs that need a full CI run.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants