GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — test: use spawnSyncAndAssert in windowsHide test by ganjanggejang · Pull Request #65351 · nodejs/node

Conversation

@ganjanggejang

@ganjanggejang ganjanggejang commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Replace the manual status, signal, stdout and stderr assertions with
spawnSyncAndAssert() from test/common/child_process.

The previous code asserted the status first, so a CI failure only
reported the exit status and the child's output was never shown. On
failure the helper prints stdout, stderr, status, signal and the
command that was run.

Only changed sync spawn(), because there is no async helper yet.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@ganjanggejang
test: use spawnSyncAndAssert in windowsHide test
ab91b39
Signed-off-by: Junsoo Ha <[email protected]>
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to Node.js core tests and test infrastructure. labels Aug 17, 2026
aduh95
aduh95 approved these changes Aug 17, 2026
View reviewed changes
@aduh95 aduh95 added author ready PRs with CI started, the required approvals, and no outstanding review comments. request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. labels Aug 17, 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 Aug 17, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@codecov

codecov Bot commented Aug 17, 2026 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.11%. Comparing base (cc60845) to head (ab91b39).
⚠️ Report is 112 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #65351      +/-   ##
==========================================
- Coverage   90.13%   90.11%   -0.02%     
==========================================
  Files         752      752              
  Lines      251820   251820              
  Branches    47352    47350       -2     
==========================================
- Hits       226974   226934      -40     
- Misses      16158    16229      +71     
+ Partials     8688     8657      -31     

see 52 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

lpinca
lpinca approved these changes Aug 17, 2026
View reviewed changes
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
jasnell
jasnell approved these changes Aug 17, 2026
View reviewed changes
@nodejs-github-bot

nodejs-github-bot commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/75962/

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

StefanStojanovic
StefanStojanovic approved these changes Aug 18, 2026
View reviewed changes
@ganjanggejang ganjanggejang mentioned this pull request Aug 18, 2026
test: use common/child_process spawnSync helpers #65377
Merged
@aduh95 aduh95 added the commit-queue PRs queued for automated landing through the Commit Queue. label Aug 18, 2026
@nodejs-github-bot nodejs-github-bot added commit-queue-failed PRs whose Commit Queue landing failed and need manual intervention before retrying. and removed commit-queue PRs queued for automated landing through the Commit Queue. labels Aug 19, 2026
@nodejs-github-bot

nodejs-github-bot commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator
Commit Queue failed
- Loading data for nodejs/node/pull/65351
✔  Done loading data for nodejs/node/pull/65351
----------------------------------- PR info ------------------------------------
Title      test: use spawnSyncAndAssert in windowsHide test (#65351)
   ⚠  Could not retrieve the email or name of the PR author's from user's GitHub profile!
Branch     ganjanggejang:replace-spawnsync -> nodejs:main
Labels     test, author ready, needs-ci, commit-queue
Commits    1
 - test: use spawnSyncAndAssert in windowsHide test
Committers 1
 - Junsoo Ha <[email protected]>
PR-URL: https://github.com/nodejs/node/pull/65351
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stefan Stojanovic <[email protected]>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/65351
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stefan Stojanovic <[email protected]>
--------------------------------------------------------------------------------
   ℹ  This PR was created on Mon, 17 Aug 2026 11:58:51 GMT
   ✔  Approvals: 4
   ✔  - Antoine du Hamel (@aduh95) (TSC): https://github.com/nodejs/node/pull/65351#pullrequestreview-4951952749
   ✔  - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/65351#pullrequestreview-4953484636
   ✔  - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/65351#pullrequestreview-4955316846
   ✔  - Stefan Stojanovic (@StefanStojanovic): https://github.com/nodejs/node/pull/65351#pullrequestreview-4959345464
   ✘  GitHub CI is still running
   ℹ  Last Full PR CI on 2026-08-18T07:17:53Z: https://ci.nodejs.org/job/node-test-pull-request/75962/
- Querying data for job/node-test-pull-request/75962/
✔  Build data downloaded
   ✔  Last Jenkins CI successful
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncu
https://github.com/nodejs/node/actions/runs/32251410497
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@daeyeon daeyeon added request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. and removed commit-queue-failed PRs whose Commit Queue landing failed and need manual intervention before retrying. labels Aug 20, 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 Aug 20, 2026
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot

This comment was marked as outdated.

Sign in to view
@nodejs-github-bot

nodejs-github-bot commented Aug 23, 2026

Copy link
Copy Markdown
Collaborator

CI: https://ci.nodejs.org/job/node-test-pull-request/76289/

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@trivikr trivikr added the commit-queue PRs queued for automated landing through the Commit Queue. label Aug 23, 2026
@nodejs-github-bot
nodejs-github-bot merged commit de31195 into nodejs:main Aug 23, 2026
97 checks passed

Uh oh!

There was an error while loading. Please reload this page.

@nodejs-github-bot

nodejs-github-bot commented Aug 23, 2026

Copy link
Copy Markdown
Collaborator

Landed in de31195

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@nodejs-github-bot nodejs-github-bot removed the commit-queue PRs queued for automated landing through the Commit Queue. label Aug 23, 2026
aduh95 pushed a commit that referenced this pull request Aug 25, 2026
@ganjanggejang @aduh95
test: use spawnSyncAndAssert in windowsHide test
8359ed9
Signed-off-by: Junsoo Ha <[email protected]>
PR-URL: #65351
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stefan Stojanovic <[email protected]>
aduh95 pushed a commit that referenced this pull request Aug 25, 2026
@ganjanggejang @aduh95
test: use spawnSyncAndAssert in windowsHide test
359369e
Signed-off-by: Junsoo Ha <[email protected]>
PR-URL: #65351
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stefan Stojanovic <[email protected]>
@github-actions github-actions Bot mentioned this pull request Aug 25, 2026
2026-08-26, Version 26.8.0 (Current) #65551
Merged
aduh95 pushed a commit that referenced this pull request Aug 27, 2026
@ganjanggejang @aduh95
test: use spawnSyncAndAssert in windowsHide test
170e563
Signed-off-by: Junsoo Ha <[email protected]>
PR-URL: #65351
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stefan Stojanovic <[email protected]>
@DevJunz DevJunz mentioned this pull request Sep 1, 2026
test: use spawnSync helpers in cpu-prof tests #65694
Closed
@github-actions github-actions Bot mentioned this pull request Sep 7, 2026
2026-09-08, Version 24.21.0 'Krypton' (LTS) #65873
Merged
aduh95 pushed a commit that referenced this pull request Sep 7, 2026
@ganjanggejang @aduh95
test: use spawnSyncAndAssert in windowsHide test
b3b1a9d
Signed-off-by: Junsoo Ha <[email protected]>
PR-URL: #65351
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stefan Stojanovic <[email protected]>
aduh95 pushed a commit that referenced this pull request Sep 7, 2026
@ganjanggejang @aduh95
test: use spawnSyncAndAssert in windowsHide test
421ee11
Signed-off-by: Junsoo Ha <[email protected]>
PR-URL: #65351
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Stefan Stojanovic <[email protected]>
panva pushed a commit that referenced this pull request Sep 25, 2026
@DevJunz @panva
test: use spawnSync helpers in cpu-prof tests
d78337f
The cpu-prof tests hand-rolled a partial version of what
test/common/child_process already provides: log the child's stderr
when the status is non-zero, then assert the status. That manual
version never shows stdout, the signal, or the command that ran, so
a CI failure gives less information than the helper would.

Replace those blocks with spawnSyncAndExitWithoutError(). Every
existing expectation is preserved -- status 0 is still required, and
signal null is now checked as well, matching the helper defaults.

Only success-path blocks whose assertions map one-to-one onto the
helper defaults are converted.

Refs: #65351
Refs: #65552
Assisted-by: claude:opus-5
Signed-off-by: Junhwan Choi <[email protected]>
PR-URL: #65694
Reviewed-By: Luigi Pinca <[email protected]>
aduh95 pushed a commit that referenced this pull request Sep 27, 2026
@DevJunz @aduh95
test: use spawnSync helpers in cpu-prof tests
d602808
The cpu-prof tests hand-rolled a partial version of what
test/common/child_process already provides: log the child's stderr
when the status is non-zero, then assert the status. That manual
version never shows stdout, the signal, or the command that ran, so
a CI failure gives less information than the helper would.

Replace those blocks with spawnSyncAndExitWithoutError(). Every
existing expectation is preserved -- status 0 is still required, and
signal null is now checked as well, matching the helper defaults.

Only success-path blocks whose assertions map one-to-one onto the
helper defaults are converted.

Refs: #65351
Refs: #65552
Assisted-by: claude:opus-5
Signed-off-by: Junhwan Choi <[email protected]>
PR-URL: #65694
Reviewed-By: Luigi Pinca <[email protected]>
HoonDongKang pushed a commit to HoonDongKang/node that referenced this pull request Sep 28, 2026
@DevJunz @HoonDongKang
test: use spawnSync helpers in cpu-prof tests
8ffb715
The cpu-prof tests hand-rolled a partial version of what
test/common/child_process already provides: log the child's stderr
when the status is non-zero, then assert the status. That manual
version never shows stdout, the signal, or the command that ran, so
a CI failure gives less information than the helper would.

Replace those blocks with spawnSyncAndExitWithoutError(). Every
existing expectation is preserved -- status 0 is still required, and
signal null is now checked as well, matching the helper defaults.

Only success-path blocks whose assertions map one-to-one onto the
helper defaults are converted.

Refs: nodejs#65351
Refs: nodejs#65552
Assisted-by: claude:opus-5
Signed-off-by: Junhwan Choi <[email protected]>
PR-URL: nodejs#65694
Reviewed-By: Luigi Pinca <[email protected]>
aduh95 pushed a commit that referenced this pull request Sep 28, 2026
@DevJunz @aduh95
test: use spawnSync helpers in cpu-prof tests
7b1c74e
The cpu-prof tests hand-rolled a partial version of what
test/common/child_process already provides: log the child's stderr
when the status is non-zero, then assert the status. That manual
version never shows stdout, the signal, or the command that ran, so
a CI failure gives less information than the helper would.

Replace those blocks with spawnSyncAndExitWithoutError(). Every
existing expectation is preserved -- status 0 is still required, and
signal null is now checked as well, matching the helper defaults.

Only success-path blocks whose assertions map one-to-one onto the
helper defaults are converted.

Refs: #65351
Refs: #65552
Assisted-by: claude:opus-5
Signed-off-by: Junhwan Choi <[email protected]>
PR-URL: #65694
Reviewed-By: Luigi Pinca <[email protected]>
aduh95 pushed a commit that referenced this pull request Oct 23, 2026
@DevJunz @aduh95
test: use spawnSync helpers in cpu-prof tests
bf467d4
The cpu-prof tests hand-rolled a partial version of what
test/common/child_process already provides: log the child's stderr
when the status is non-zero, then assert the status. That manual
version never shows stdout, the signal, or the command that ran, so
a CI failure gives less information than the helper would.

Replace those blocks with spawnSyncAndExitWithoutError(). Every
existing expectation is preserved -- status 0 is still required, and
signal null is now checked as well, matching the helper defaults.

Only success-path blocks whose assertions map one-to-one onto the
helper defaults are converted.

Refs: #65351
Refs: #65552
Assisted-by: claude:opus-5
Signed-off-by: Junhwan Choi <[email protected]>
PR-URL: #65694
Reviewed-By: Luigi Pinca <[email protected]>
aduh95 pushed a commit that referenced this pull request Oct 28, 2026
@DevJunz @aduh95
test: use spawnSync helpers in cpu-prof tests
962f52c
The cpu-prof tests hand-rolled a partial version of what
test/common/child_process already provides: log the child's stderr
when the status is non-zero, then assert the status. That manual
version never shows stdout, the signal, or the command that ran, so
a CI failure gives less information than the helper would.

Replace those blocks with spawnSyncAndExitWithoutError(). Every
existing expectation is preserved -- status 0 is still required, and
signal null is now checked as well, matching the helper defaults.

Only success-path blocks whose assertions map one-to-one onto the
helper defaults are converted.

Refs: #65351
Refs: #65552
Assisted-by: claude:opus-5
Signed-off-by: Junhwan Choi <[email protected]>
PR-URL: #65694
Reviewed-By: Luigi Pinca <[email protected]>
aduh95 pushed a commit that referenced this pull request Nov 11, 2026
@DevJunz @aduh95
test: use spawnSync helpers in cpu-prof tests
457ac17
The cpu-prof tests hand-rolled a partial version of what
test/common/child_process already provides: log the child's stderr
when the status is non-zero, then assert the status. That manual
version never shows stdout, the signal, or the command that ran, so
a CI failure gives less information than the helper would.

Replace those blocks with spawnSyncAndExitWithoutError(). Every
existing expectation is preserved -- status 0 is still required, and
signal null is now checked as well, matching the helper defaults.

Only success-path blocks whose assertions map one-to-one onto the
helper defaults are converted.

Refs: #65351
Refs: #65552
Assisted-by: claude:opus-5
Signed-off-by: Junhwan Choi <[email protected]>
PR-URL: #65694
Reviewed-By: Luigi Pinca <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jasnell jasnell jasnell approved these changes
@lpinca lpinca lpinca approved these changes
@StefanStojanovic StefanStojanovic StefanStojanovic approved these changes
@aduh95 aduh95 aduh95 approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. needs-ci PRs that need a full CI run. test Issues and PRs related to Node.js core tests and test infrastructure.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

8 participants

@ganjanggejang @nodejs-github-bot @jasnell @lpinca @StefanStojanovic @aduh95 @daeyeon @trivikr
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.