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
Commit cdc78ec
Browse filesBrowse the repository at this point in the historyBrowse files
fix(gate): scope lock decisions to the gate environment
Pass the environment to acquireValidationLock so nested-owner detection and
the gate runner read the same variables, skip the lock on unsupported hosts,
cover signal cancellation, and tighten the lock documentation.
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Copy file name to clipboardExpand all lines: docs/agents/testing.md
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,10 @@
10
10
Serialized validation requires macOS or Linux.
11
11
On Windows, use plan mode or focused checks.
12
12
Both broad commands acquire the same host lock.
13
-
So do `pnpm gate` ids `unit`, `unit-ci`, `provider-integration`, `fuzz-parsers`, `mutation`, `mutation-affected`, and `concurrency-torture`.
14
-
A heavy gate in a locked validation inherits the lock. GitHub runners skip it.
13
+
These `pnpm gate` ids acquire the same lock:`unit`, `unit-ci`, `provider-integration`, `fuzz-parsers`, `mutation`, `mutation-affected`, and `concurrency-torture`.
14
+
A gate inside a locked validation reuses that lock. A GitHub runner takes no lock.
15
15
Wait for the owner to finish, or cancel your waiter with Ctrl-C.
16
-
Do not delete lock files.
17
-
A wait ends after two hours. Nested validation fails immediately.
16
+
A wait ends after two hours. A nested `pnpm check` or `pnpm check:affected --run` fails immediately.
18
17
Focused tests do not lock. Avoid subprocess-heavy tests beside a broad gate.
19
18
20
19
The runner prints progress and a receipt path. The receipt contains:
@@ -46,7 +45,6 @@ A full selection for these changes is intentional.
46
45
Read `failOpenReasons` in plan JSON or `plan.failOpenReasons` in a receipt.
47
46
Do not reduce selection to get a pass.
48
47
49
-
Read required-check status on the PR.
50
48
The receipt lists skipped checks and owners in `results[].reason`.
0 commit comments