test: avoid initial-break wait in restart-message#62060
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #62060 +/- ##
==========================================
- Coverage 90.05% 90.04% -0.02%
==========================================
Files 714 714
Lines 225242 225242
Branches 42579 42570 -9
==========================================
- Hits 202843 202809 -34
- Misses 14187 14203 +16
- Partials 8212 8230 +18 🚀 New features to boost your workflow:
|
Commit Queue failed- Loading data for nodejs/node/pull/62060 ✔ Done loading data for nodejs/node/pull/62060 ----------------------------------- PR info ------------------------------------ Title test: avoid initial-break wait in restart-message (#62060) ⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile! Branch inoway46:fix-flaky-debugger-restart -> nodejs:main Labels test, needs-ci Commits 1 - test: avoid initial-break wait in restart-message Committers 1 - inoway46 <inoueyuya416@gmail.com> PR-URL: https://github.com/nodejs/node/pull/62060 Refs: https://github.com/nodejs/node/issues/61762 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/62060 Refs: https://github.com/nodejs/node/issues/61762 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> -------------------------------------------------------------------------------- ℹ This PR was created on Sun, 01 Mar 2026 15:42:47 GMT ✔ Approvals: 1 ✔ - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/62060#pullrequestreview-3884836184 ✔ Last GitHub CI successful ✘ No Jenkins CI runs detected -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/23564673240 |
|
Since the Windows flakiness seems better now, could you please rerun CI for this PR? |
3aa0054 to
6611c3b
Compare
| // For `restart`, sync on attach/prompt instead of BREAK_MESSAGE to avoid flaky races. | ||
| // https://github.com/nodejs/node/issues/61762 | ||
| await cli.command('restart'); | ||
| await cli.waitFor(/Debugger attached\./); |
There was a problem hiding this comment.
Leaving this unchanged because this path has not shown the flake again since the fix two months ago.
ok may be the stronger sync point here too, but I’ll handle that in a separate PR after further investigation.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
I just noticed that the commit is missing the DCO sign-off, so I’ll need to amend it and force-push. Unfortunately, this will invalidate the current CI run. Sorry for the churn, and thank you for starting the CI. cc @cola119 |
Signed-off-by: inoway46 <inoueyuya416@gmail.com>
0fa8b47 to
eb34825
Compare
|
The latest full CI has passed. Could someone land this PR when they have a chance? Thank you! |
|
Landed in 3163d8a. |
Summary
Follow-up to #61773
test/parallel/test-debugger-restart-message.jscan still flake on macOS unusual-path runs at the initialwaitForInitialBreak(). This change syncs startup on the debugger CLI'sokconnection-completion output plus the prompt.failed CI log (main branch): https://github.com/nodejs/node/actions/runs/22545396955
Testing
./tools/test.py -p actions parallel/test-debugger-restart-message./tools/test.py -p actions -j1 --repeat 40 parallel/test-debugger-restart-messageRefs: #61762