Repository navigation
fix(repo): draw every deciding timeout class in the timeout-fields property - #146
Merged
ryanleecode merged 2 commits intoOct 2, 2026
Merged
ryanleecode merged 2 commits into
ryanleecode merged 2 commits into
Conversation
Verdict-Semantics: unchanged
…operty Verdict-Semantics: unchanged
systemfsoftware-maker
added this pull request to stack #152
October 2, 2026 01:45
ryanleecode
removed this pull request from stack #152
October 2, 2026 17:36
ryanleecode
changed the base branch from
main
to
feat/agent-ready-failure-diagnostics
October 2, 2026 17:36
ryanleecode
added this pull request to stack #157
October 2, 2026 17:36
ryanleecode
merged commit Oct 2, 2026
25fdbe7
into
feat/agent-ready-failure-diagnostics
10 checks passed
ryanleecode
approved these changes
Oct 2, 2026
ryanleecode
left a comment
Contributor
There was a problem hiding this comment.
Reviewed by the merge conductor as part of the diagnostics stack. CI green on this head except where noted in the stack summary (macOS timeouts on #151 are flaky: the same code is green on macOS in #155 and #156; the #156 stryker-js mutation shard times out until main records its first full-cost timing, as this PR's description says). Merging into feat/agent-ready-failure-diagnostics with a merge commit.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Layer 1 of the agent-ready failure diagnostics stack (docs/plans/2026-10-01-2306-feat-agent-ready-failure-diagnostics-plan.md, unit U1).
Mutation run 36935602456 failed shard 1/6 in its dry run: the in-source property
mse_MutantStatusAndEvidence_PersistedTimeoutFieldsFollowTheReproductionRuledrew too few inputs to tell the timeout-fields subject apart from a constant, so the fork refused it as vacuous under the mutation-worker budget (30 runs, seed 1). The CI summary then reported this as an "infrastructure failure".TestRunner.HitLimitReasonTextaccepts only the canonicalHit limit reached (count/limit)shape.Verified: the property passes under seeds 1-20 at the worker budget, and
stryker run --dryRunOnlyon packages/stryker-js succeeds.