(MOT-4299) fix(ci): free runner disk before the Harness E2E stack build - #700
Conversation
The harness 1.7.1 release died in the deployed-E2E validation packaging harness-e2e-stack.tar.gz: the registry-mode stack build fills a standard runner's 14GB of free disk (ENOSPC, reproduced on rerun). Drop the preinstalled toolchains this job never uses (~30GB: dotnet, Android, GHC, CodeQL, docker images) before building.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
skill-check — worker0 verified, 54 skipped (no docs/).
Four for four. Nicely done. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe E2E build workflow now frees runner disk space before checkout. It removes unused toolchains, prunes Docker images without failing the job, and reports filesystem usage. ChangesWorkflow maintenance
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…runner (#701) Registry mode builds only harness/target/release/harness-e2e; nothing creates the repo-root target/ directory the packaging step writes into (source mode gets it from the engine install). Both harness release attempts died on this step: 1.7.1 masked as ENOSPC by the full runner disk, 1.7.2 as a clean ENOENT once #700 freed the space. The registry E2E path has never executed past this point.
The harness 1.7.1 release (run 30963283418) cleared the fixed candidate gate (#698) and quickstart, then died in Validate candidate in deployed Harness E2E / harness e2e build:
ENOSPC — the registry-mode stack build fills the standard runner's ~14GB free disk. Reproduced identically on a failed-jobs rerun, so it's structural, not runner variance (this is the first harness staged release to reach this stage).
Fix: drop preinstalled toolchains the job never uses (~30GB: dotnet, Android SDK, GHC/ghcup, CodeQL, docker images) as the first step of the shared
buildjob, with adf -hfor observability. Benefits both source and registry modes.Evidence gating context:
release_candidate.pyrequiresharness_e2e == successin the same run, and a release rerun uses the tag's workflow snapshot — so this fix can only take effect through a new tag (1.7.2) after merge. Ref #699 for the broader re-run idempotency issue.Summary by CodeRabbit