Repository navigation
perf(ci): run the ARC voice and inbox check as parallel cached jobs - #151
Conversation
The single Voice + founder inbox job ran every typecheck, test and both builds on one runner with caching off, so each run took 11-15 minutes and queued behind itself. Split it into core, web and mobile workers that run together, and keep the required check name on a small aggregator that fails unless all three succeeded. Dependencies now install through the shared cache action, the Playwright browser is cached, and a release-branch push or pull request can save the pnpm store instead of only the stale default branch. Model: grok/grok-4.7 Task: implementation Agent: Builder Lane: magpie Harness: t3
The aggregator used if: always(), which also runs when the workflow is cancelled, and a worker that never started reports success. A new push cancels the previous run, so the required check would have gone green for a run whose tests never started. It now runs only when the workflow was not cancelled, and the coverage guard rejects both that condition and a test path that only appears inside dead code. The pnpm store save goes back to the action's original condition. This fork's default branch is release/native-0.1.10, so the push to it already writes the store every later run reads, and a pull request cache would only have been readable by that one PR. Model: grok/grok-4.7 Task: fix Agent: Builder Lane: magpie Harness: t3
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
Focused re-check of both findings on |
…/arc-ci-parallel-cache Keep the fork drift receipt from #147 and the three cached ARC workers from this branch. The receipt runs on the core worker after setup-ci-deps provides Node, and it still unshallows the shallow checkout before it measures history. Model: grok/grok-4.7 Task: conflict Agent: Builder Lane: magpie Harness: t3
|
Note 🤖 Grok 4.7 responding on behalf of nullStack65 Resolved the merge conflict with The core worker still installs through Verified on that head before push: YAML |
The founder-inbox job checked out only .github and ran the coverage script with node, but the ARC image has no node on PATH, so the step exited 127. Provide libatomic, then setup-node from package.json, before that script. The guard fails if that order is removed. Model: grok-4.7 Task: fix Agent: Builder Lane: grok Harness: t3
Problem
The required ARC check
Voice + founder inbox (Linux ARC)ran every typecheck, all 48 tests and both builds as one serial job with caching switched off. Recent runs onrelease/native-0.1.10took 11 to 15 minutes (for example run 44807747792 took 14m42s), and the single self-hosted runner queued the next run behind it.Fix
The job splits into three workers that run at the same time on
t3code-ci-arc: core (typecheck, server tests, server build), web (web tests and the web build) and mobile (mobile tests and the Playwright voice latency test). A small aggregator job keeps the exact nameVoice + founder inbox (Linux ARC)that therelease-native-protectionruleset requires, and it fails unless all three workers succeeded. It does not run when the workflow was cancelled, so a run that gets cancelled while its workers are still queued cannot report the required check green.Dependencies install through the existing
.github/actions/setup-ci-depsaction, which caches the Vite+ home, the pnpm store and the lockfile verification record withactions/cache. The Playwright Chromium shell gets its own cache keyed on the lockfile. Only the core job saves the pnpm store, so the three jobs do not race to reserve one key. The store save keeps the action's original condition: the push to the default branch, which on this fork isrelease/native-0.1.10, writes the store every later run reads..github/scripts/arc-ci-coverage.cjsfails the required check if a worker stops running one of the 48 tests the serial job ran, or if the aggregator would run on a cancelled workflow.node --test .github/scripts/arc-ci-coverage.test.cjspasses, 4 of 4, and actionlint reports no findings once the self-hosted runner label is configured.Review
One independent review round on grok/grok-4.7 returned two Important findings: the aggregator ran on cancellation, and the widened pnpm store save wrote a cache only one pull request could read. Both are fixed in
61b4730db8and sent back for a focused re-check of those two findings only.Deploy: none
Model: grok/grok-4.7
Task: implementation