Troubleshooting

General

container: seems to be ignored, or steps run on the host The runner label in runs-on is registered in host mode. Use a label that's backed by Docker or Podman. See Getting Started.

node: not found / JavaScript action fails You're using a JavaScript action (for example actions/checkout) in an image without Node.js. Use checkout instead.

Permission denied while installing packages The container isn't running as root. These actions don't use sudo. Use an image that runs as root, or set options: --user root under container:.

checkout

git is not installed and no supported package manager was found The image has no git and none of the supported package managers. Use an image that has one of them, or bake git into your image.

Authentication failed / repository not found The workflow token can't read the repository, for example when the target is a different private repo. Pass token: with a personal access token that has read access.

git describe fails / no tags Tags aren't fetched. Use fetch-depth: "0" and add a git fetch --tags step.

rebar3-ci

bash: not found The image has no bash (for example an Alpine erlang:*-alpine image). Use the Debian-based erlang:* images.

Warnings don't fail the build Add warnings_as_errors to erl_opts in rebar.config. See rebar3-ci.

lisp-ci

lisp-ci needs an apt-based image (debian, ubuntu) Switch to an image such as debian:forky or debian:trixie.

no SBCL release for aarch64 / no CCL release for aarch64 Upstream only publishes x86-64 Linux binaries. Run the job on an x86-64 runner.

curl: (22) The requested URL returned error: 404 while installing SBCL sbcl-version doesn't exist on SourceForge, or that release has no x86-64-linux-binary tarball. Check the file listing.

The CCL install step hangs at ccl --version This was seen once during testing, in a debian:forky container: the job sat on ccl --version for more than 10 minutes, while an identical run went through normally. The cause isn't known yet. If it keeps happening, add timeout-minutes: to the job so it can't hang forever, and please open an issue.

unsupported lisp 'X' (expected sbcl or ccl) lisps contains something other than sbcl or ccl.

Exit code 2 with Component "..." not found test-system doesn't match an ASDF system in the project, or that system's dependencies aren't in the qlfile.

Exit code 2 with a package error mentioning the test system The Parachute package must have the same name as the test system (for example cl-ft2/test). See lisp-ci.

Exit code 1 but no visible failures Parachute prints its report above the exit. Scroll up in the step's log for the failing tests.

Errors loading a foreign library The shared library isn't installed. Add its Debian package to packages.

Tests from an earlier features set still run Pass force: "true" on every call after the first, so the fasls are rebuilt.