ci: kernel-build artifact upload is best-effort (storage-quota resilience)

The kernel build itself is the gate; uploading the zImage/dtb can fail on an
account-wide GitHub artifact-storage-quota hit unrelated to the build. Mark the
upload continue-on-error so a good build isn't red-X'd by it. Outputs also remain
on the self-hosted runner host.

Verified: kernel-build compiled the RV1106 6.18.46 kernel end-to-end on
bfe-mpc-0640 (zImage 8.25 MB + rv1106-warden.dtb 37 KB); the patch series applied
(issue #1 fix confirmed).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017wB8KB3MMQztRDXCMCkPrf
This commit is contained in:
BFE Engineering
2026-08-25 17:16:36 -06:00
co-authored by Claude Opus 4.8
parent 5e1b02ba60
commit a804a35e08
+5
View File
@@ -135,7 +135,12 @@ jobs:
# the ephemeral Luckfox SDK checkout path.
CROSS_COMPILE: arm-linux-gnueabihf-
run: bash build/build-kernel.sh
# Best-effort: the build IS the gate. Uploading the zImage/dtb to GitHub
# artifact storage can fail on an account-wide storage-quota hit (recalculated
# every 6-12h) that has nothing to do with this build — don't red-X a good
# kernel build over it. The outputs also remain on the self-hosted runner host.
- uses: actions/upload-artifact@v4
continue-on-error: true
with:
name: kernel-rv1106
path: |