Skip to content
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

test_runner: remove runtime experimental warning #44844

Merged
merged 1 commit into from Oct 3, 2022

Conversation

cjihrig
Copy link
Contributor

@cjihrig cjihrig commented Sep 30, 2022

This commit removes the experimental warning that is emitted when the test runner is used. The test runner feature is still considered experimental, but this change makes its output easier to read.

This commit removes the experimental warning that is emitted
when the test runner is used. The test runner feature is still
considered experimental, but this change makes its output
easier to read.
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. labels Sep 30, 2022
MoLow
MoLow approved these changes Oct 1, 2022
@tniessen
Copy link
Member

tniessen commented Oct 1, 2022

±0 as long as it remains experimental. (If it's just in the docs, it's easy to ignore, so if we later break the test runner, it might make users who rely on it unhappy.)

@cjihrig
Copy link
Contributor Author

cjihrig commented Oct 1, 2022

A couple notes:

  • It would definitely still be considered experimental. I also think we should try to avoid breaking changes to the test runner at this point.
  • Currently, the warning is emitted for every test file. When using the CLI runner with many files, this can get noisy if there are failures across several files. Fortunately, this only shows up for tests with failures, but...
  • There is ongoing work to add a TAP parser which would ideally surface user output to both stdout and stderr, which would make the current behavior noisy even if nothing fails.
  • There is prior art for dropping the runtime warning when it interferes with the usability of the feature. I'm thinking of util.parseArgs() specifically, but there are probably others.

@MoLow MoLow added test_runner dont-land-on-v14.x PRs that should not land on the v14.x-staging branch and should not be released in v14.x. and removed test Issues and PRs related to the tests. labels Oct 2, 2022
jasnell
jasnell approved these changes Oct 2, 2022
@nodejs-github-bot
Copy link
Contributor

@nodejs-github-bot
Copy link
Contributor

@nodejs-github-bot
Copy link
Contributor

@cjihrig cjihrig added the commit-queue Add this label to land a pull request using GitHub Actions. label Oct 3, 2022
@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Oct 3, 2022
@nodejs-github-bot nodejs-github-bot merged commit ad8442f into nodejs:main Oct 3, 2022
57 checks passed
@nodejs-github-bot
Copy link
Contributor

Landed in ad8442f

TimShilov pushed a commit to TimShilov/node that referenced this pull request Oct 3, 2022
This commit removes the experimental warning that is emitted
when the test runner is used. The test runner feature is still
considered experimental, but this change makes its output
easier to read.

PR-URL: nodejs#44844
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: James M Snell <jasnell@gmail.com>
panva pushed a commit to panva/node that referenced this pull request Oct 4, 2022
This commit removes the experimental warning that is emitted
when the test runner is used. The test runner feature is still
considered experimental, but this change makes its output
easier to read.

PR-URL: nodejs#44844
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: James M Snell <jasnell@gmail.com>
danielleadams pushed a commit that referenced this pull request Oct 11, 2022
This commit removes the experimental warning that is emitted
when the test runner is used. The test runner feature is still
considered experimental, but this change makes its output
easier to read.

PR-URL: #44844
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: James M Snell <jasnell@gmail.com>
MoLow pushed a commit to MoLow/node that referenced this pull request Nov 23, 2022
This commit removes the experimental warning that is emitted
when the test runner is used. The test runner feature is still
considered experimental, but this change makes its output
easier to read.

PR-URL: nodejs#44844
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: James M Snell <jasnell@gmail.com>
MoLow pushed a commit to MoLow/node that referenced this pull request Dec 9, 2022
This commit removes the experimental warning that is emitted
when the test runner is used. The test runner feature is still
considered experimental, but this change makes its output
easier to read.

PR-URL: nodejs#44844
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: James M Snell <jasnell@gmail.com>
@cjihrig cjihrig deleted the remove-warning branch December 30, 2022 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dont-land-on-v14.x PRs that should not land on the v14.x-staging branch and should not be released in v14.x. needs-ci PRs that need a full CI run. test_runner
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants