test: show more information in test-http2-debug upon failure

[joyeecheung]

Use spawnSyncAndAssert() so that the stderr is logged when it doesn't match expectations.

Refs: #58353

[nodejs-github-bot]

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.24%. Comparing base (4454d09) to head (855d596).
Report is 117 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #58391      +/-   ##
==========================================
+ Coverage   90.12%   90.24%   +0.11%     
==========================================
  Files         629      633       +4     
  Lines      186628   186902     +274     
  Branches    36622    36692      +70     
==========================================
+ Hits       168206   168663     +457     
+ Misses      11216    11046     -170     
+ Partials     7206     7193      -13     

see 98 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.

[richardlau]

Use spawnSyncAndAssert() so that the stderr is logged when it doesn't match expectations.

Refs: #58353

So typically CI for this PR doesn't fail so we don't have the extra information to help diagnose the failures 😂.

FWIW I kicked off stress runs (1000 times) for this PR and they didn't fail either: https://ci.nodejs.org/view/Stress/job/node-stress-single-test/574/

Trying again with 10000 repetitions: https://ci.nodejs.org/view/Stress/job/node-stress-single-test/575/

[joyeecheung]

Somehow the stress test doesn't make it show up. I guess we need to wait for it to show up in the CI then..

[github-actions]

Fast-track has been requested by @joyeecheung. Please 👍 to approve.

[joyeecheung]

Adding fast-track since this looks trivial enough and helps us get more information from the CI.

[joyeecheung]

(Also, if it cannot be reproduced in stress test, but can still show up in the CI, maybe it is caused by interaction with other tests, in that case moving it to sequential maybe a good enough band-aid)

[nodejs-github-bot]

Landed in 0bbe5d3