-
-
Notifications
You must be signed in to change notification settings - Fork 0
CI: flip Idris2 ABI Proofs to strict (remove continue-on-error) #34
Copy link
Copy link
Open
Labels
bindingsABI, FFI, WASM, and cross-language interop surfacesABI, FFI, WASM, and cross-language interop surfaceschoreRoutine maintenance with no behaviour changeRoutine maintenance with no behaviour changecicdCI/CD: workflows, actions, lockfiles, pins, runners, release gatesCI/CD: workflows, actions, lockfiles, pins, runners, release gates
Description
Activity
Metadata
Metadata
Assignees
Labels
bindingsABI, FFI, WASM, and cross-language interop surfacesABI, FFI, WASM, and cross-language interop surfaceschoreRoutine maintenance with no behaviour changeRoutine maintenance with no behaviour changecicdCI/CD: workflows, actions, lockfiles, pins, runners, release gatesCI/CD: workflows, actions, lockfiles, pins, runners, release gates
Follow-up to #29 / #31 (Wave-3 Chapel rehabilitation).
The
check-abijob in.github/workflows/hpc-ci.ymlcurrently hascontinue-on-error: truewith comment "Idris2 CI setup can be fragile". Empirically: on the rerun of #31, this job failed withidris2: command not foundafter the Idris2 source-bootstrap step. The source-bootstrap is the fragile bit, not docudactyl's proofs.To flip the job to strict:
make bootstrap SCHEME=chezschemesource build with either:packinstall (Idris2 package manager) — pulls a tested binary, fast install.idris-community/Idris2-pre-built-packageor equivalent.stefan-hoeck/setup-idris2if it exists.continue-on-error: truefrom the job.This isn't a docudactyl correctness issue — it's CI hygiene + faster feedback. The actual ABI proofs in
src/Docudactyl/ABI/are the strict gate worth recovering.Related: see
feedback_pre_compact_discipline/ estate CI hygiene practices.