-
-
Notifications
You must be signed in to change notification settings - Fork 3k
test(ci): heartbeat + running-test pointer to debug the silent backend-test ELIFECYCLE #7838
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
Merged
JohnMcLear
merged 7 commits into
develop
from
test-ci-diagnostics-heartbeat-currenttest
May 25, 2026
+127
−14
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
aa79a34
test(ci): heartbeat + running-test pointer in backend test diagnostics
JohnMcLear 9b79a76
fix: heartbeat _getActiveHandles optional chain bug (Qodo #2)
JohnMcLear be5defc
test(ci): per-test start diag + drop stray console.log noise
JohnMcLear b7ff499
test(ci): write node-report on every heartbeat tick
JohnMcLear 3965680
fix: writeReport with bare filename, not mixed-slash absolute path
JohnMcLear 2897d34
test(ci): write node-report on test boundaries, throttled to 4Hz
JohnMcLear 8a0b030
test(ci): drop beforeEach report throttle from 250ms to 100ms
JohnMcLear File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Heartbeat logging lacks feature flag
📘 Rule violation⚙ MaintainabilityAgent Prompt
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation toolsThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concern #2 (the optional-chain TypeError) is fixed in 9b79a76 — capture the array first, read
.lengthonly when it exists, keep-1as the "API missing" sentinel. Good catch.Concern #1 (feature flag): respectfully disagreeing.
diagnostics.tsis a temporary debug-only bootstrap (top-of-file comment: "Drop this file once the flake's root cause is identified and fixed.") wired in viamocha --requirein the backendtestscript. The whole file is already opt-in at the test-runner layer — adding an internal flag would just multiply the existing toggle, and defaulting it off would silence the diagnostic in CI which is the one environment where the silent flake reliably reproduces. The repo's pattern for diagnostic instrumentation (see PR #7663, which added the unhandled-rejection logger with no flag) is to land it unguarded and remove the file once the kill is rooted. Keeping that pattern here.