You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci(chapel): bump 2.3.0→2.8.0 + libunwind-dev preinstall to fix the link-phase exec ENOENT
PR #141's chapel-build job consistently fails at `Make Binary - Linking`
with `error in exec: No such file or directory` — the chpl 2.3.0 .deb
omits the bundled LLVM backend, so when the typecheck step tries to link
libproven.so via `chpl ... -lproven`, chpl exec()'s a clang/lld it
doesn't ship.
The PR author validated locally with chpl 2.8.0; align CI with that.
Pattern mirrors sibling estate repo panic-attack/chapel-ci.yml which has
been running 2.8.0 green since the chapel rehab (PRs #85/#86/#88/#89/#90,
2026-05-30).
Changes:
- CHAPEL_VERSION 2.3.0 → 2.8.0; URL + SHA256 repinned
(944a454b8a791f344312fcd261b562871159b74f5ef41d81e11833eb21d85f60,
verified out-of-band against the GitHub Releases asset).
- All four install blocks (chapel-build, chapel-symbol-audit,
chapel-smoke, chapel-tests) preinstall libunwind-dev (the chpl-built
binaries' runtime link-time dep on the ubuntu .deb path) and drop the
CHPL_HOME / CHPL_TARGET_* env overrides — 2.8.0 auto-configures its
target tuple correctly, so the 2.3.0-era runtime-tuple workaround is
obsolete (verified against panic-attack).
- Each install block now ends with `chpl --version` as the version
probe (consistent across all four).
Net: -73/+30 lines.
Source fix, not bypass — the .deb-toolchain mismatch caused the failure
and bumping to a self-contained toolchain removes the root cause.
Refs #141.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments