Repository navigation
/ship's test step says when it hits its time limit, and long test file lists no longer overflow the remote command (GST-2958) - #4429
Merged
Conversation
…ts off the remote test command line gstack-ship-preflight stopped gstack-pregate after a fixed hour and printed 'PREGATE: unreadable (exit 143)'. The whole step's budget is now --step-timeout <s> (default 3600), and a stop at it prints 'PREGATE: time limit hit' with the way out: push and let CI's full run carry the tests, or a larger budget. The test_backend command pregate prints for a small machine put every selected file into one argument, which Linux refuses past 128 KiB. The files now reach the VM in a setup script named by its content. Also adds an arg-limit troubleshooting entry and says the Windows job has eight shards. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
|
😎 This pull request was merged. |
…folder path test The remote command now names a setup script instead of the files, so the test checks that the script lists the ./-prefixed path. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
A selected test path containing a newline, or equal to the list's end marker, could end the setup script's file list early and run the rest as shell on the test VM. Such paths now keep the quoted inline command. Review-Finding: p1/outside-voice#1 reader=outside-voice Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Merged
capy-ai Bot
added a commit
that referenced
this pull request
Nov 17, 2026
- /autoplan's approval page no longer hides a reviewer's product objection behind "keep your direction". (#4431) - Every skill that loads the shared preamble, on every host, now says to ask a question once and to check a file before handing it over. (#4383) - The Captain manuals now name the `Failed or skipped:` and `Also changed:` lines that READY and lane reports carry. (#4432) - gstack's shell locks hold again on Ubuntu 26.04, where `mkdir` reports success when another process won the race (GST-2247). (#4262) - `test/gstack-lock-race.test.ts` runs the old pattern and the helper against a PATH shim that behaves like uutils 0.8.0 `mkdir`, so it runs on any runner image: the old pattern lets two of four racers win, the helper admits exactly one in each of 60 races and never overlaps across take, hold and release loops, and parallel `gstack-config` writers keep every key. (#4262) - Windows Setup E2E now runs when `bin/gstack-lock.sh` changes. (#4433) - Claude Code's skill list now says when to use each gstack skill, so Opus loads /review and /plan-eng-review when a request fits. (#4387) - A pull request's merge head can no longer keep its `/ship` receipt without a full review. (#4365) - `/ship` now counts review rounds per pull request, and the head that merges always gets a full review. (#4360) - /ship's documentation audit no longer accepts a passing result when an earlier line from the same audit said "blocked". (#4434) - /ship's documentation audit no longer spends an attempt when the audit child writes text after its result. (#4285) - The README lists the two new guides, and the install doc counts its hooks right. (#4403) - docs/releases.md now says the stable release cut treats a failed commit status as red and a pending one as still going, as it has since #4257. (#4436) - /ship's `finish --docs-requested` now accepts a docs fix when the audit named the file with a line number. (#4437) - Document the `.gstack/approval-classes.json` schema, `gstack-approval-classes` CLI commands, and owner approval citation format in `docs/ship-policy.md#approval-classes`. (#4355) - `/eval-plan` now runs four result checks instead of leaving them to judgment. (#4384) - The /review coverage-audit eval no longer fails a run that really read the source file when zsh stops a command line at an `echo ====` separator. (#4364) - Sixteen in-repo documentation links reach their section again. (#4394) - gstack agents now open every status report with what failed, what they didn't verify and what else they changed. (#4273) - Two new short guides. (#4380) - A skill you wrote whose contract still lists `check_after_last_edit` keeps the rest of its contract. (#4439) - The ship policy guide now explains how to merge any pull request with `gstack-ship-queue land`, even in a repository with one maintainer. (#4377) - /ship's test step runs a large unit suite on Linux. (#4426) - Every skill that loads the shared preamble, on every host, now says never to print a whole environment, git config or process table. (#4382) - Pull requests from /ship now open with at most three plain lines, and every merge lands as one commit titled with the PR title. (#4438) - `gstack-pr-wait`, `gstack-ci-gate` and the release cut no longer call a commit green while a check on it failed. (#4257) - `gstack-runaway` now says what a thread's cold and empty wakes cost, not just how many there were (GST-2770). (#4385) - The optional Stop hook no longer checks for a test run after the last edit, and /verify asks for it in plain words instead. (#4428) - /ship's test step says when it ran out of time, and you can set its budget. (#4429) - The remote test command no longer puts every file on one command line. (#4429) - The stable release no longer waits on the nightly Windows tests (GST-2815). (#4400) - Ubicloud fan-outs can no longer overshoot the vCPU limit, and owners no longer delete each other's VMs. (#4430) - hono is pinned to 4.13.16, which fixes five advisories the weekly OSV scan found in 4.13.13 (gstack#4406). (#4408) - `package.json` overrides (#4408) - `test/dependency-security.test.ts`: the lockfile floor check now covers `hono >= 4.13.16`. (#4408) - The nightly Windows test run finishes again. (#4409) - A short write-up checklist in ETHOS.md. (#4381) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
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.
/ship's test step now says when it runs out of time and lets you set its budget, and the remote test command no longer packs every test file into one command-line argument, which Linux refuses past 128 KiB.
You don't need to do anything: the default budget is still one hour, and
--step-timeout <s>ongstack-ship-preflightraises it.Details
What changed
gstack-ship-preflight --step-timeout <s>(1 to 86400, default 3600) sets the budget for the whole test step. When a run hits it, the output says so and names the way out:(Captured on this branch with a 2-second budget in a throwaway clone. Before this change the same stop printed
PREGATE: unreadable (exit 143).)arg-limitentry, and docs/pregate.md describes both changes.Why
"PREGATE: unreadable (exit 143)" told nobody that the suite simply ran past the hour /ship gave it. Now the stop says it hit the time limit and how to get past it. Separately, a large selection made the remote test command too long for Linux to start, and now the command stays short however many files are selected.
Blast radius
The changes stay inside
gstack-ship-preflight's test step and the command pregate prints for a remote test backend. Pregate never runs that command itself. The default budget is the same 3600 s as the old fixed limit, and a run that finishes in time takes the same path as before (lib/ship-preflight.ts, read). Bun'sspawnSyncsetsETIMEDOUTwhen the limit hits, and pregate's SIGTERM handler kills the test processes it supervises (walked failure path; QA probe 005 found no test process left behind).Summary
Long suites and big selections both failed in ways that hid the cause. The test step now has a budget you can set and a clear message when it runs out. The remote command passes its file list through a setup script. After review, odd file names fall back to the old quoted form.
Test Coverage
All new code paths have test coverage: each of the 4 changed runtime files has a changed test that names it.
--step-timeoutprints the time-limit line and the way out; bad values are usage errors.Tests ran: test 1678 (files)
Pre-Landing Review
Two rounds:
REVIEW_LOOP: passes=2 blocking_found=1 deferred=0 noted=3 fixed=1 scope=frozen unbound=1 ledgers_read=3 dispatches=8
Gate edits: none detected (6 listed, 3 read; patterns: RH-1,RH-3,RH-4,RH-12,RH-13,RH-14,RH-15,RH-16; unlisted idioms: none)
Second-model review (openai/gpt-6.1-sol): completed, 1 blocking finding, fixed.
Review notes
These are below the blocking floor (advisory, informational, test-gap or wording items). They are recorded here and not fixed in this PR.
lib/pregate/checks/lanes.ts:521Two pregate runs with the same selection rewrite the same content-named setup file without an atomic write. If the runner reads it mid-rewrite, it could see an empty list.lib/pregate/checks/lanes.ts:528The printed command now names a file on this machine, so it fails elsewhere or after the state root is cleaned. In the scratch fallback its path changes every run, so a later clear never matches.lib/pregate/checks/lanes.ts:519Old setup scripts are never pruned. Each is a few KB, one per distinct selection.lib/pregate/checks/lanes.ts:518The end-marker branch of the new guard has no test of its own.lib/pregate/checks/lanes.ts:578The declaredremote_gateroute (scripts/ubicloud/pregate-remote.sh) has the same newline problem. That code predates this PR.lib/pregate/checks/lanes.ts:518On a very large selection that also holds an odd path, the quoted fallback can exceed the argument limit and fail loudly.Exploratory QA
Pass, 5 captures in a throwaway clone with its own state root:
--helpdocuments the option.--step-timeout 0and86401exit 2 with a usage message.Limits: the budget ran out during pregate's own checks, before the slow test started. The stop also took about 19 s of wall time for a 2-second budget, because pregate cleans up after SIGTERM.
TODOS
The 3600 s preflight and
finishwrapper deadline (P3) is narrowed tofinish's half. The preflight half is done in this PR.Documentation
Scope: This audit covered the committed changes in base 2af3822..84c9e0d at reviewed tree 4486a9a9b0ba9de0c74ebdb2669580f7ff9d6fc9. Those changes add the
--step-timeoutoption with itsPREGATE: time limit hitoutput, move the remote file list into a setup script, and describe the Windows free tests as eight shards instead of six. The working tree had no staged, unstaged or new files.Result: The docs were already current, so I edited nothing. docs/pregate.md covers the time limit in the
timeout_srow, and TODOS.md has a matching note. The move of the remote file list into a setup script is covered in the remote gate section and thearg-limitrow of docs/pregate.md, and docs/troubleshooting.md has a newarg-limitentry. Both anchors resolve. The eight-shard wording matches .github/workflows/windows-free-tests.yml and agrees with docs/support-tiers.md. No ship template or README mentions the preflight time budget or the oldPREGATE: unreadable (exit 143)output, so no template needs to be regenerated. The banned-terms check found nothing because main has no .gstack/banned-terms.json.Debt: None. The changelog fragment and the TODOS.md edit belong to the parent ship run, so I read them but did not change them.
Test plan
Agent notes
Lane GSTA-576 for GST-2958. Refs GST-2958
Approvals
No approvals recorded for branch ship-step-time-limit-and-remote-file-lists.
Plan: exempt: bug fix (failing-first tests on main, no plan review)
Plan check: exempt bug fix
REVIEW_LOOP: passes=2 blocking_found=1 deferred=0 noted=3 fixed=1 scope=frozen unbound=1 ledgers_read=3 dispatches=8
Gate edits: none detected (6 listed, 3 read; patterns: RH-1,RH-3,RH-4,RH-12,RH-13,RH-14,RH-15,RH-16; unlisted idioms: none)
CI_CARRY: accepted ci-carry tree=4486a9a9b0ba tests=37412 runs=44087393983/1 profiles=ci-reuse/free-tests heads=84c9e0da3f66
PREGATE: requires-remote cleared (final tree)