Skip to content

ci: fail the release if the migration tarball exceeds the 2GB-board RAM budget #522

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mrosseel wants to merge 1 commit into
base: release
Choose a base branch
from
Open

ci: fail the release if the migration tarball exceeds the 2GB-board RAM budget #522

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -299,6 +299,17 @@ jobs:
boot rootfs | zstd -T0 -19 -o "release/pifinder-migration-${TAG}.tar.zst"
sudo rm -rf /tmp/tarball-staging

# Never-again guard (2026-07-05 field failure): during migration the
# tarball is copied into RAM, so a 2GB board can only hold ~1.4GB.
# Refuse to publish a release that cannot migrate 2GB boards.
MIG_MB=$(( $(stat -c%s "release/pifinder-migration-${TAG}.tar.zst") / 1048576 ))
BUDGET_MB=800
echo "migration tarball: ${MIG_MB}MB (budget ${BUDGET_MB}MB)"
if [ "${MIG_MB}" -gt "${BUDGET_MB}" ]; then
echo "::error::migration tarball ${MIG_MB}MB exceeds ${BUDGET_MB}MB budget — shrink the migration closure (check linux-firmware and friends)"
exit 1
fi

# Checksum sidecars. The in-app upgrade (PiFinder.sys_utils) fetches
# <artifact-url>.sha256 and refuses to flash without a matching digest;
# it reads the first whitespace-delimited token, so sha256sum output is
Expand Down
Loading