Skip to content

test: deflake inspector setup and runner timeouts - #66255

Open
panva wants to merge 2 commits into
nodejs:mainfrom
panva:deflake-inspector-runner-run
Open

panva wants to merge 2 commits into
nodejs:mainfrom
panva:deflake-inspector-runner-run

Conversation

@panva

@panva panva commented Sep 24, 2026

Copy link
Copy Markdown
Member

https://github.com/nodejs/reliability/blob/main/reports/2026-09-24.md

  • In test-inspector-async-hook-setup-at-signal, defer timeout creation with setImmediate so async-hook activation requested during a V8 interrupt can finish first.
  • In test-runner-run, use a dedicated fixture with a pending promise and assertion plan, removing competing assertion timers while preserving both timeout-failure checks.

@panva panva added flaky-test Issues and PRs involving tests that fail intermittently in CI. commit-queue-rebase PRs the Commit Queue should land as multiple self-contained commits. labels Sep 24, 2026
@nodejs-github-bot

Copy link
Copy Markdown
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 Node.js core tests and test infrastructure. labels Sep 24, 2026
Async hook activation can be deferred when the inspector command arrives
during a V8 interrupt. Schedule timeout creation with setImmediate so
the event loop finishes enabling the hooks before recording its async
stack.

Signed-off-by: Filip Skokan <panva.ip@gmail.com>
Assisted-by: Codex
Use a dedicated fixture with a pending promise and assertion plan
instead of competing assertion timers. Keep both timeout failure
assertions and clear the keepalive interval after the tests finish.

Signed-off-by: Filip Skokan <panva.ip@gmail.com>
Assisted-by: Codex
@panva
panva force-pushed the deflake-inspector-runner-run branch from a373d46 to b7526ad Compare September 24, 2026 07:43
@codecov

codecov Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.30%. Comparing base (a2c8da5) to head (b7526ad).
⚠️ Report is 28 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #66255      +/-   ##
==========================================
+ Coverage   90.28%   90.30%   +0.01%     
==========================================
  Files         789      789              
  Lines      272878   272878              
  Branches    52097    52105       +8     
==========================================
+ Hits       246360   246409      +49     
+ Misses      16975    16917      -58     
- Partials     9543     9552       +9     

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

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@panva panva added author ready PRs with CI started, the required approvals, and no outstanding review comments. commit-queue PRs queued for automated landing through the Commit Queue. labels Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. commit-queue PRs queued for automated landing through the Commit Queue. commit-queue-rebase PRs the Commit Queue should land as multiple self-contained commits. flaky-test Issues and PRs involving tests that fail intermittently in CI. 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

Development

Successfully merging this pull request may close these issues.

3 participants