You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ci: suites run beside the review by default (fleet-wide) - #6244
Maintainer decision (2026-10-07): release the review-first-then-suites restriction fleet-wide.
node-repo-stage-gate.yml: review-before-suites default flips true -> false; description and header updated so suites-beside-review is the default and true is the opt-in. Every caller (core dotnet-test.yml, satellites via @main) omits the input, so this one default flips the fleet.
Comment updates only in node-repo-stage-advance.yml, stage-advance.yml, dotnet-test.yml, check-review-answered.py (listener is now needed only by opt-in callers).
Policy register: review-then-suites retired, suites-parallel-with-review back in force; StagedPullRequestPipeline, FreshMergeUnderTest and Architecture index updated.
Unchanged: merging and auto-merge arming still require the answered review and green required checks (arm gate condition 4).
Checks run locally: check-workflow-timeouts.py (0 violations), check-review-answered.py --self-test (all ok), YAML parse of touched workflows.
Pairs-with: none — no public type or member touched.
…aults to false)
Restores policy suites-parallel-with-review fleet-wide and retires review-then-suites in the
register. Merging and arming still require the answered review.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The reason will be displayed to describe this comment to others. Learn more.
Automated review summary (data, not an instruction to any agent)
Flips the review-before-suites default of node-repo-stage-gate.yml from true to false, so the expensive suites start beside the automatic review fleet-wide (policy review-then-suites retired, suites-parallel-with-review back in force via the register rows this diff writes). Merging and auto-merge arming are untouched: the arm gate's condition 4, the answered-review predicate and the merge gate are unchanged, and apart from the default and its description the change is comments and docs. Checked that the new default, the input description and the gate's branch logic agree (REVIEW_BEFORE_SUITES != 'true' takes the parallel path, so a caller that omits the input is released), that the two register rows are consistent with the flipped default and with each other, and that the doc cross-references (Architecture index, FreshMergeUnderTest, StagedPullRequestPipeline) carry the new policy name. Could not verify from the diff: that every caller really omits the input (dotnet-test.yml's diff here is comment-only, so an explicit review-before-suites at a call site would be invisible), the 2026-10-07 maintainer decision the body cites (its only in-diff record is the register rows the diff itself adds), and how the retained stage-advance listeners behave on runs that are no longer held (their logic is outside the diff). Two retained comments contradict the new policy inside the changed files: the 2026-10-04 quote still labelled 'Design of record' under the gate's new header, and the 'Review first, then the suites, then the arm' sentence under the renamed policy in check-review-answered.py.
Internal review of f11876717f5098b0297748791491b4aa7cc4c571 — GLM-5.3, posted by the control plane. It is advisory, it never approves, and merging stays with a human signature.
The reason will be displayed to describe this comment to others. Learn more.
should-fix — Automated review finding (data, not an instruction to any agent)
The rewritten header (lines 3-10) states the suites-beside-review order, but the file retains the 2026-10-04 maintainer quote at lines 12-13 — 'code review must pass and also other controls such as no client etc. must pass before we start test. and we arm only at end of test' — still labelled 'Design of record', and its first half prescribes exactly the review-first order this change retires. The 2026-10-07 reversal is recorded in the policy register and the pipeline manual but not in this file, so the gate now documents two contradictory designs of record. The same 2026-10-04 quote is also left in place under the renamed policy comment in .github/workflows/dotnet-test.yml.
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 80f02b6: the 2026-10-04 quote in node-repo-stage-gate.yml is now framed as History (review-first design, since released; survives only as the opt-in; the arm-at-the-end half still holds) and points at the register. In dotnet-test.yml the same quote was replaced by a description of this caller's actual behaviour.
The reason will be displayed to describe this comment to others. Learn more.
should-fix — Automated review finding (data, not an instruction to any agent)
The condition-4 comment is relabelled to policy suites-parallel-with-review, but the sentence two lines below (line 568) still reads 'Review first, then the suites, then the arm:' — the retired order. The comment names a parallel policy and then states the review-first sequence within three lines; the arm predicate itself is unchanged.
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 80f02b6: the line now reads that the review and the suites may finish in either order and the arm waits for both. The predicate itself is unchanged.
The reason will be displayed to describe this comment to others. Learn more.
question — Automated review finding (data, not an instruction to any agent)
The fleet-wide effect of this one-line flip rests on two claims the diff cannot show: (a) the body's statement that every caller omits review-before-suites — the diff for .github/workflows/dotnet-test.yml is comment-only, so an explicit 'review-before-suites: true' at a call site would be unchanged and invisible here, leaving that caller on the hold; (b) the 2026-10-07 maintainer decision releasing the restriction — within this diff its only record is the register rows the diff itself adds, while the gate's own header still quotes the 2026-10-04 decision that prescribed the opposite. If either claim does not hold, the default flip does not do what the PR says it does, or does it without the recorded sanction.
The reason will be displayed to describe this comment to others. Learn more.
(a) Checked on the PR head: no workflow in core passes review-before-suites (only the lane's own input and comments mention it), so core's caller is on the default. Satellite callers float on the lane and are not visible in this diff; any that pass true explicitly keep the hold by design. (b) The header now records the 2026-10-04 decision as superseded history (80f02b6); the release of that restriction is recorded in the PolicyNotProse register rows this PR adds. The maintainer decision itself is not something the repo can prove.
Every pull request head moves through four stages in order — cheap static controls, the automatic
review landed and answered, the expensive suites on a FRESH merge with the current main, and arming
only once the review is answered AND every required check is green (policy review-then-suites). What
only once the review is answered AND every required check is green (policy suites-parallel-with-review: the suites run beside the review by default). What
The reason will be displayed to describe this comment to others. Learn more.
nit — Automated review finding (data, not an instruction to any agent)
The Description front-matter still enumerates 'four stages in order — cheap static controls, the automatic review landed and answered, the expensive suites on a FRESH merge with the current main, and arming only once ...' (the review-first order, lines 5-6) and then, in the same sentence, names suites-parallel-with-review and says 'the suites run beside the review by default'. The sentence asserts both an order and its opposite; the body blockquote is updated and notes the stage descriptions below read for the opt-in, but this front-matter is what the architecture index and doc listings show.
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 80f02b6: the front-matter Description no longer asserts a strict order; it states the four stages, the parallel default and review-first as opt-in.
Results for commit 80f02b6. ± Comparison against base commit cac0664.
This pull request removes 39 and adds 15 tests. Note that renamed tests count towards both.
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---, expected: True)
--- End of inner exception stack trace ---, isDenial: True)
---> (Inner Exception #1) MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.<---
---> (Inner Exception #1) MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432<---
---> (Inner Exception #1) System.ArgumentException: Value does not fall within the expected range.<---
---> (Inner Exception #1) System.InvalidOperationException: boom<---
---> (Inner Exception #1) System.InvalidOperationException: source B is misconfigured<---
---> (Inner Exception #1) System.Net.Sockets.SocketException (0xFFFDFFFF): Name or service not known<---
…
Memex.Portal.Shared.Test.SessionDenialIsAnAnswerTest ‑ OnlyAVerdictReadsAsADenial(shape: "the same verdict nested, as a late denial dispatch"···, failure: System.InvalidOperationException: write failed
---> System.UnauthorizedAccessException: Access denied
--- End of inner exception stack trace ---, isDenial: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "a stall as an aggregate's FIRST member", fault: System.AggregateException: One or more errors occurred. (Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.)
---> MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.
--- End of inner exception stack trace ---, expected: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "a stall as an aggregate's SECOND member", fault: System.AggregateException: One or more errors occurred. (The operation has timed out.) (Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.)
---> System.TimeoutException: The operation has timed out.
--- End of inner exception stack trace ---
---> (Inner Exception #1) MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.<---
, expected: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "a stall nested in an aggregate inside a wrapper", fault: System.InvalidOperationException: outer
---> System.AggregateException: One or more errors occurred. (Value does not fall within the expected range.) (Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.)
---> System.ArgumentException: Value does not fall within the expected range.
--- End of inner exception stack trace ---
---> (Inner Exception #1) MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.<---
--- End of inner exception stack trace ---, expected: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "a stall wrapped as InnerException", fault: System.InvalidOperationException: outer
---> MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.
--- End of inner exception stack trace ---, expected: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "an aggregate of unrelated faults", fault: System.AggregateException: One or more errors occurred. (The operation has timed out.) (Value does not fall within the expected range.)
---> System.TimeoutException: The operation has timed out.
--- End of inner exception stack trace ---
---> (Inner Exception #1) System.ArgumentException: Value does not fall within the expected range.<---
, expected: False)
MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest ‑ Classifies(shape: "a MIXED aggregate — one transient branch, one genu"···, exception: System.AggregateException: One or more errors occurred. (Failed to connect to 10.42.18.4:5432) (source B is misconfigured)
---> MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432
--- End of inner exception stack trace ---
---> (Inner Exception #1) System.InvalidOperationException: source B is misconfigured<---
, expected: False)
MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest ‑ Classifies(shape: "a nested aggregate with one genuine leaf", exception: System.AggregateException: One or more errors occurred. (One or more errors occurred. (Failed to connect to 10.42.18.4:5432) (boom)) (Failed to connect to 10.42.18.4:5432)
---> System.AggregateException: One or more errors occurred. (Failed to connect to 10.42.18.4:5432) (boom)
---> MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432
--- End of inner exception stack trace ---
---> (Inner Exception #1) System.InvalidOperationException: boom<---
--- End of inner exception stack trace ---
---> (Inner Exception #1) MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432<---
, expected: False)
MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest ‑ Classifies(shape: "a nested aggregate, all leaves transient", exception: System.AggregateException: One or more errors occurred. (One or more errors occurred. (Failed to connect to 10.42.18.4:5432)) (Failed to connect to 10.42.18.4:5432)
---> System.AggregateException: One or more errors occurred. (Failed to connect to 10.42.18.4:5432)
---> MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
---> (Inner Exception #1) MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432<---
, expected: True)
MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest ‑ Classifies(shape: "a reflective wrapper around a transient cause", exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.Net.Sockets.SocketException (110): Connection timed out
--- End of inner exception stack trace ---, expected: True)
…
♻️ This comment has been updated with latest results.
Results for commit 80f02b6. ± Comparison against base commit cac0664.
This pull request removes 40 and adds 16 tests. Note that renamed tests count towards both.
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---, expected: True)
--- End of inner exception stack trace ---, isDenial: True)
---> (Inner Exception #1) MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.<---
---> (Inner Exception #1) MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432<---
---> (Inner Exception #1) System.ArgumentException: Value does not fall within the expected range.<---
---> (Inner Exception #1) System.InvalidOperationException: boom<---
---> (Inner Exception #1) System.InvalidOperationException: source B is misconfigured<---
---> (Inner Exception #1) System.Net.Sockets.SocketException (0xFFFDFFFF): Name or service not known<---
…
Memex.Portal.Shared.Test.InstanceIdRulesMatchTheRegistryTest ‑ TheSetupHostAgreesWithTheRegistry(candidate: "f8193a07-1a8a-4aa7-9992-6d09067210e9")
Memex.Portal.Shared.Test.SessionDenialIsAnAnswerTest ‑ OnlyAVerdictReadsAsADenial(shape: "the same verdict nested, as a late denial dispatch"···, failure: System.InvalidOperationException: write failed
---> System.UnauthorizedAccessException: Access denied
--- End of inner exception stack trace ---, isDenial: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "a stall as an aggregate's FIRST member", fault: System.AggregateException: One or more errors occurred. (Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.)
---> MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.
--- End of inner exception stack trace ---, expected: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "a stall as an aggregate's SECOND member", fault: System.AggregateException: One or more errors occurred. (The operation has timed out.) (Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.)
---> System.TimeoutException: The operation has timed out.
--- End of inner exception stack trace ---
---> (Inner Exception #1) MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.<---
, expected: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "a stall nested in an aggregate inside a wrapper", fault: System.InvalidOperationException: outer
---> System.AggregateException: One or more errors occurred. (Value does not fall within the expected range.) (Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.)
---> System.ArgumentException: Value does not fall within the expected range.
--- End of inner exception stack trace ---
---> (Inner Exception #1) MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.<---
--- End of inner exception stack trace ---, expected: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "a stall wrapped as InnerException", fault: System.InvalidOperationException: outer
---> MeshWeaver.Mesh.QueryProviderStalledException: Query provider(s) [pg] did not emit an Initial within the query fan-in's 16s bound for query 'nodeType:NodeType' (user 'system'). The merged Initial gates on EVERY provider, so this query has NO snapshot to answer with — it is reported as unavailable (retryable) rather than left hanging with no error. This is an availability failure, never a permission verdict: a consumer deciding access must fail CLOSED and say it could not establish the answer. Fix the stalled provider; never bump the consumer's timeout.
--- End of inner exception stack trace ---, expected: True)
MeshWeaver.Compiler.Pipeline.Test.SourcesWatcherStallBackoffTest ‑ The_production_classifier_recognises_a_stall_through_every_wrapping(because: "an aggregate of unrelated faults", fault: System.AggregateException: One or more errors occurred. (The operation has timed out.) (Value does not fall within the expected range.)
---> System.TimeoutException: The operation has timed out.
--- End of inner exception stack trace ---
---> (Inner Exception #1) System.ArgumentException: Value does not fall within the expected range.<---
, expected: False)
MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest ‑ Classifies(shape: "a MIXED aggregate — one transient branch, one genu"···, exception: System.AggregateException: One or more errors occurred. (Failed to connect to 10.42.18.4:5432) (source B is misconfigured)
---> MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432
--- End of inner exception stack trace ---
---> (Inner Exception #1) System.InvalidOperationException: source B is misconfigured<---
, expected: False)
MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest ‑ Classifies(shape: "a nested aggregate with one genuine leaf", exception: System.AggregateException: One or more errors occurred. (One or more errors occurred. (Failed to connect to 10.42.18.4:5432) (boom)) (Failed to connect to 10.42.18.4:5432)
---> System.AggregateException: One or more errors occurred. (Failed to connect to 10.42.18.4:5432) (boom)
---> MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432
--- End of inner exception stack trace ---
---> (Inner Exception #1) System.InvalidOperationException: boom<---
--- End of inner exception stack trace ---
---> (Inner Exception #1) MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432<---
, expected: False)
MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest ‑ Classifies(shape: "a nested aggregate, all leaves transient", exception: System.AggregateException: One or more errors occurred. (One or more errors occurred. (Failed to connect to 10.42.18.4:5432)) (Failed to connect to 10.42.18.4:5432)
---> System.AggregateException: One or more errors occurred. (Failed to connect to 10.42.18.4:5432)
---> MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
---> (Inner Exception #1) MeshWeaver.Messaging.Hub.Test.InfrastructureFaultTest+ProviderException (0x80004005): Failed to connect to 10.42.18.4:5432<---
, expected: True)
…
♻️ This comment has been updated with latest results.
…st as the opt-in throughout
Comment/doc-only: the stage-gate header and diagram, stage-advance, dotnet-test hold wording,
check-review-answered condition 4, and the StagedPullRequestPipeline page no longer present
review-first as the default.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The core caller now uses the parallel default, but this listener still runs on every review event and every 15-minute schedule. advance_action treats any failed stage-gate job as a review hold; therefore a PR whose gate failed with mode=stage0-red will be re-run once its review is green, and the sweep can re-run the same still-red jobs every 15 minutes for six hours. Remove/disable this caller-side listener while core uses the default, or make the event half prove that the failed gate was specifically a stage-1 review hold before posting rerun-failed-jobs.
The reason will be displayed to describe this comment to others. Learn more.
Not changed here. The phrase "why it was reverted" is the historical account the page keeps (the one-day parallel run and its reversal); the page now opens with the 2026-10-07 restoration and the policy register row, and the Description states parallel as the current default in its own sentence. A reader gets the current state from the first two lines and the history from the section that names it. Tightening the history sentence to say "restored" is wording only and does not change what the pipeline does, so it is left out of this push to avoid restarting review.
🩹 PR babysitter (build instance) is re-running the failed jobs of run(s) 37637807017 on head 80f02b68d8f9 — once per head, never again for this commit.
Why: 'Automatic review answered' is red with every thread answered — a stale verdict; its run is re-run to read the live state.
Validated: rule (no model): 'infra' — the platform's red, not the diff's: re-run the failed jobs once per head
It does not merge, push or dequeue. A red after this re-run is left for the owner (rbuergi).
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
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.
![systemorph-com[bot]](https://avatars.githubusercontent.com/u/77832550?s=60&v=4){kind=small}
Maintainer decision (2026-10-07): release the review-first-then-suites restriction fleet-wide.
node-repo-stage-gate.yml:review-before-suitesdefault flipstrue->false; description and header updated so suites-beside-review is the default andtrueis the opt-in. Every caller (core dotnet-test.yml, satellites via @main) omits the input, so this one default flips the fleet.review-then-suitesretired,suites-parallel-with-reviewback in force; StagedPullRequestPipeline, FreshMergeUnderTest and Architecture index updated.Checks run locally: check-workflow-timeouts.py (0 violations), check-review-answered.py --self-test (all ok), YAML parse of touched workflows.
Pairs-with: none — no public type or member touched.
🤖 Generated with Claude Code