SilverLABS/SilverMetal
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

ci(windows): free build working set before the persist copy (persist OOM) #28

Merged
SilverLABS merged 1 commits from ci/free-before-persist into main 2026-06-10 15:35:35 +00:00
Conversation 0 Commits 1 Files Changed 1 +9
SilverLABS commented 2026-06-10 15:35:23 +00:00
Owner
Copy Link

Symptom

Build #111 got all the way through driver-inject + ISO repack + validation, then failed at "Persist build output to stable path": Copy-Item … 'C:\silvermetal\out\' → "There is not enough space on the disk".

Cause

The build's working set under RUNNER_TEMP (extracted ISO tree + the mounted/expanded install.wim ~15-20 GB + the 5 GB base ISO + the 5 GB output) fills the single-volume runner. By persist time there's < 5 GB free for the second 5 GB copy. The image grew again with the injected NetKVM driver.

Fix

Before the persist copy, delete RUNNER_TEMP\smbuild + RUNNER_TEMP\base.iso (no longer needed once the ISO is built + validated) to reclaim ~10 GB. The ISO itself lives in RUNNER_TEMP\out (untouched; the SBOM/SHA/ISO uploads still read from there).

Test Plan

  • YAML validates
  • Build green: driver injects, ISO persists to C:\silvermetal\out

🤖 Generated with Claude Code

## Symptom Build #111 got all the way through driver-inject + ISO repack + validation, then failed at **"Persist build output to stable path"**: `Copy-Item … 'C:\silvermetal\out\'` → *"There is not enough space on the disk"*. ## Cause The build's working set under `RUNNER_TEMP` (extracted ISO tree + the mounted/expanded `install.wim` ~15-20 GB + the 5 GB base ISO + the 5 GB output) fills the single-volume runner. By persist time there's < 5 GB free for the second 5 GB copy. The image grew again with the injected NetKVM driver. ## Fix Before the persist copy, delete `RUNNER_TEMP\smbuild` + `RUNNER_TEMP\base.iso` (no longer needed once the ISO is built + validated) to reclaim ~10 GB. The ISO itself lives in `RUNNER_TEMP\out` (untouched; the SBOM/SHA/ISO uploads still read from there). ## Test Plan - [x] YAML validates - [ ] Build green: driver injects, ISO persists to `C:\silvermetal\out` 🤖 Generated with [Claude Code](https://claude.com/claude-code)
SilverLABS added 1 commit 2026-06-10 15:35:23 +00:00
ci(windows): free build working set before persist copy (oscdimg OK, persist OOM)
Some checks failed
Build SilverMetal Enhanced - Windows ISO / build (pull_request) Failing after 45s
Details
9fa613b8c1 
Build got through the ISO repack but failed copying the 5GB ISO to C:\silvermetal\out
('not enough space'): the build's working set (extracted ISO tree + expanded install.wim
+ 5GB base ISO) fills the single-volume runner, leaving <5GB for the persist copy. The
image grew again with the injected driver. Delete RUNNER_TEMP\smbuild + base.iso (no
longer needed post-build/validate) right before the copy to reclaim ~10GB.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
SilverLABS merged commit 541a17c792 into main 2026-06-10 15:35:35 +00:00
SilverLABS deleted branch ci/free-before-persist 2026-06-10 15:35:35 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
SilverLABS
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SilverLABS/SilverMetal#28
Delete Branch "ci/free-before-persist"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?