Skip to content

Isolate bridge verification from unrelated Gradle builds - #598

Open
bringhurst wants to merge 3 commits into
3.9-li-bridge/interrupted-deletion-recoveryfrom
3.9-li-bridge/verifier-process-isolation
Open

bringhurst wants to merge 3 commits into
3.9-li-bridge/interrupted-deletion-recoveryfrom
3.9-li-bridge/verifier-process-isolation

Conversation

@bringhurst

Copy link
Copy Markdown
Member

The bridge verifier ran gradlew --stop in both checkouts before starting the broker test. Gradle's daemon registry is shared; those commands are not limited to this verification and can stop an unrelated build.

All verifier and staging Gradle invocations already use --no-daemon. Remove the global stop commands and the evidence rows that required them. Single-use Gradle processes exit after their command. Command timeouts still terminate only the process groups started by the verifier.

The new dry-run regression inspects the actual full command plan. It fails before on --stop and requires every direct Gradle command to use --no-daemon. All 85 Python tests and actual RAT pass after the change. No source, wrapper, archive, phase, record or protocol check is removed.

This affects only the upgrade verifier. It does not change broker/client behavior, the client bootstrap configuration, or the independent CI foundations. Based on #597. Final-pair qualification and the F28 client-profile decision remain open.

@bringhurst
bringhurst added this pull request to stack #582 September 11, 2026 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant