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: force spec reporter in test-runner-watch-mode.mjs #54538

Merged
merged 1 commit into from
Aug 26, 2024

Conversation

cjihrig
Copy link
Contributor

@cjihrig cjihrig commented Aug 24, 2024

In the CI this test generates TAP output that can confuse the Python test runner. Avoid the problem by not outputting TAP at all.

Fixes: #54535

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/test_runner

@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 Aug 24, 2024
@cjihrig cjihrig added the commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. label Aug 24, 2024
@cjihrig
Copy link
Contributor Author

cjihrig commented Aug 24, 2024

Looks like some related failures in the GitHub CI because of all the places throughout the codebase where we already set the reporter to spec. I wonder if it might be worth shipping a breaking change to use the spec reporter by default in all cases.

Copy link

codecov bot commented Aug 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.32%. Comparing base (bec3425) to head (1fc1ba8).
Report is 335 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #54538      +/-   ##
==========================================
- Coverage   87.33%   87.32%   -0.01%     
==========================================
  Files         649      649              
  Lines      182603   182603              
  Branches    35035    35036       +1     
==========================================
- Hits       159474   159457      -17     
- Misses      16396    16404       +8     
- Partials     6733     6742       +9     

see 22 files with indirect coverage changes

In the CI this test generates TAP output that can confuse the
Python test runner. Avoid the problem by not outputting TAP at
from the spawned child process.

Fixes: nodejs#54535
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Aug 25, 2024
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Aug 25, 2024
@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Aug 25, 2024

@cjihrig cjihrig added commit-queue Add this label to land a pull request using GitHub Actions. and removed needs-ci PRs that need a full CI run. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. labels Aug 25, 2024
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@nodejs-github-bot nodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Aug 26, 2024
@nodejs-github-bot nodejs-github-bot merged commit 05bd3cf into nodejs:main Aug 26, 2024
58 checks passed
@nodejs-github-bot
Copy link
Collaborator

Landed in 05bd3cf

@cjihrig cjihrig deleted the tap-fix branch August 26, 2024 13:20
RafaelGSS pushed a commit that referenced this pull request Aug 30, 2024
In the CI this test generates TAP output that can confuse the
Python test runner. Avoid the problem by not outputting TAP at
from the spawned child process.

Fixes: #54535
PR-URL: #54538
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: James M Snell <[email protected]>
RafaelGSS pushed a commit that referenced this pull request Aug 30, 2024
In the CI this test generates TAP output that can confuse the
Python test runner. Avoid the problem by not outputting TAP at
from the spawned child process.

Fixes: #54535
PR-URL: #54538
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@RafaelGSS RafaelGSS mentioned this pull request Aug 30, 2024
@targos targos added the dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. label Sep 22, 2024
louwers pushed a commit to louwers/node that referenced this pull request Nov 2, 2024
In the CI this test generates TAP output that can confuse the
Python test runner. Avoid the problem by not outputting TAP at
from the spawned child process.

Fixes: nodejs#54535
PR-URL: nodejs#54538
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI is failing because of Descending test id on line: 'ok 2 - should run tests with dependency repeatedly'
8 participants