NodetteHQ/PureYAML
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

fix(scripts): let check-wasm skip when the SDK is absent

Browse Source 
check-all.sh defines exit 77 as a non-fatal infrastructure skip and
check-linux.sh already uses it for an unreachable runner, but a missing
wasm SDK hard-failed with exit 2, blocking every push from a machine
without the toolchain. The hosted CI wasm job stays authoritative; a
machine with the SDK installed still fails hard on a real build break.
This commit is contained in:
Mihaela Mihaljevic 2026-07-12 13:32:17 +02:00
parent 6fa49b7ffc
commit 58872248d5
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
scripts/check-wasm.sh
View File

@ -14,9 +14,13 @@ swift_command() {
}
if ! swift_command sdk list | grep -qx "$SDK_ID"; then
echo "wasm: missing Swift SDK '$SDK_ID'" >&2
echo "wasm: install the SDK or set SWIFT_WASM_SDK_ID" >&2
exit 2
# A missing SDK is "infrastructure unavailable", the same class as an
# unreachable Linux runner: exit 77 so check-all.sh records a SKIP and
# the authoritative wasm gate runs on hosted CI. A machine with the SDK
# installed still fails hard on a real build break below.
echo "wasm: SKIP (missing Swift SDK '$SDK_ID' on this machine)." >&2
echo "wasm: install the SDK or set SWIFT_WASM_SDK_ID to gate locally." >&2
exit 77
fi
swift_command build --swift-sdk "$SDK_ID"