enricobuehler
64b9d11ee6
ci / web (push) Successful in 1m2s
ci / docs-site (push) Successful in 1m2s
apple / swift (push) Successful in 4m58s
ci / bench (push) Successful in 6m47s
android-screenshots / screenshots (push) Successful in 2m58s
windows-host / package (push) Successful in 14m30s
decky / build-publish (push) Successful in 16s
ci / rust (push) Successful in 18m31s
windows-msix / package (arm64, C:\Users\Public\ffmpeg-arm64, --no-default-features, aarch64-pc-windows-msvc, C:\t-a64) (push) Successful in 4m6s
android / android (push) Successful in 12m26s
windows-msix / package (x64, C:\Users\Public\ffmpeg, , x86_64-pc-windows-msvc, C:\t) (push) Successful in 3m58s
web-screenshots / screenshots (push) Successful in 2m45s
flatpak / build-publish (push) Failing after 8m2s
linux-client-screenshots / screenshots (push) Successful in 7m33s
docker / deploy-docs (push) Successful in 19s
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Successful in 9s
docker / build-push (ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 6s
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 7s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 7s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 5m35s
arch / build-publish (push) Successful in 12m58s
deb / build-publish (push) Successful in 14m8s
rpm / build-publish (44, fedora-44, punktfunk-fedora44-rpm) (push) Successful in 12m35s
release / apple (push) Successful in 28m12s
rpm / build-publish (43, bazzite, punktfunk-fedora-rpm) (push) Successful in 14m43s
apple / screenshots (push) Successful in 18m28s
A full Windows CI pass writes ~50 GB of cargo target output into the shared C:\t (x64) / C:\t-a64 (arm64) scratch dirs on the intentionally-small (100 GB) windows-amd64 runner. Left to accumulate across runs, that overflowed the disk and every build died with "no space on device" (os error 112) — bytemuck_derive, cc, bindgen, windows, tracing-subscriber, fs4 all failing mid-compile, taking down pf-vdisplay/host builds. ensure-windows-toolchain.ps1 already runs first in every Windows job, so reclaim disk there before provisioning/building: call the runner-baked reclaimer (unom/infra installs C:\Users\Public\act-runner\clean-runner-disk.ps1 + a scheduled task) in threshold mode so THIS job starts with headroom regardless of when that task last ran, and keep incremental caches warm when there's room. A small inline fallback covers a runner not yet re-baked with the reclaimer. The whole step is best-effort — a cleanup hiccup never fails the build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
50 lines
2.7 KiB
PowerShell
50 lines
2.7 KiB
PowerShell
# Idempotent pre-flight for punktfunk's Windows CI dependencies: WDK + cargo-wdk (driver builds),
|
|
# FFmpeg x64/ARM64 trees, Inno Setup, and the aarch64-pc-windows-msvc rustup target. Run at the
|
|
# start of every Windows CI job so ANY runner - freshly built from unom/infra's windows-runner/
|
|
# template, rebuilt, or a new one added later - self-provisions on first real use, instead of
|
|
# needing a human to remember to dispatch a separate provisioning workflow first (and instead of
|
|
# racing which runner a manually-dispatched provisioning workflow happens to land on, when more
|
|
# than one Windows runner shares the windows-amd64 label).
|
|
#
|
|
# Each underlying script already does its own existence checks (Test-Path/Get-Command) before
|
|
# installing anything, so this is a fast no-op on a runner that's already fully provisioned - the
|
|
# only cost is on a genuinely fresh box, where it's the first job's problem to pay once.
|
|
$ErrorActionPreference = "Stop"
|
|
trap {
|
|
Write-Host "FATAL: $_"
|
|
Write-Host $_.ScriptStackTrace
|
|
exit 1
|
|
}
|
|
|
|
# --- reclaim disk before building -----------------------------------------------------------------
|
|
# The windows-amd64 runner's system volume is intentionally small (100 GB) and a full Windows CI pass
|
|
# writes ~50 GB of cargo target output into C:\t (x64) / C:\t-a64 (arm64). Left to accumulate across
|
|
# runs that overflows the disk and the build dies with "no space on device" (os error 112) - exactly
|
|
# what took the Windows host build down. The runner bakes in a reclaimer + a scheduled task that keeps
|
|
# an idle box lean (unom/infra's setup-gitea-runner-base.ps1 ->
|
|
# C:\Users\Public\act-runner\clean-runner-disk.ps1); call it here too so THIS job starts with headroom
|
|
# regardless of when that task last ran. Threshold mode (no -Force): it only prunes when actually low,
|
|
# so incremental-compile caches survive when there's room. Best-effort - a cleanup hiccup must never
|
|
# fail the build.
|
|
$reclaimer = 'C:\Users\Public\act-runner\clean-runner-disk.ps1'
|
|
try {
|
|
if (Test-Path $reclaimer) {
|
|
& powershell.exe -NoProfile -ExecutionPolicy Bypass -File $reclaimer
|
|
}
|
|
else {
|
|
# Fallback for a runner not yet re-baked with the infra reclaimer: prune the big target dirs when low.
|
|
$freeGb = [math]::Round((Get-PSDrive C).Free / 1GB, 1)
|
|
Write-Host "[ensure-toolchain] clean-runner-disk.ps1 absent; C: free ${freeGb} GB"
|
|
if ($freeGb -lt 35) {
|
|
foreach ($d in 'C:\t', 'C:\t-a64') {
|
|
if (Test-Path $d) { Write-Host " reclaiming $d"; Remove-Item $d -Recurse -Force -ErrorAction SilentlyContinue }
|
|
}
|
|
}
|
|
}
|
|
}
|
|
catch { Write-Warning "disk reclaim step failed (non-fatal): $_" }
|
|
|
|
$ciDir = $PSScriptRoot
|
|
& "$ciDir\provision-windows-wdk.ps1"
|
|
& "$ciDir\provision-windows-punktfunk-extras.ps1"
|