Skip to content

Build build only dependencies in spack CI#720

Draft
hughcars wants to merge 3 commits intomainfrom
hughcars/eigen-spack-fix
Draft

Build build only dependencies in spack CI#720
hughcars wants to merge 3 commits intomainfrom
hughcars/eigen-spack-fix

Conversation

@hughcars
Copy link
Copy Markdown
Collaborator

@hughcars hughcars commented May 1, 2026

There are failures in CI that appear to be because a build only dependency is not built by the --only dependencies build stage, possibly due to a spack update. This PR adds a flag to also force build those stages.

https://github.com/awslabs/palace/actions/runs/25180874981/job/73825496404?pr=719

Spack develop's new installer defers build-type-only deps when
installing from cache, so `--only dependencies` skipped eigen in the
first phase and `--only package` aborted. The `--include-build-deps`
flag forces build-type deps (eigen, cmake, pkgconfig, fortran, etc.)
to install eagerly.
@hughcars hughcars added the no-long-tests This PR does not require the long tests to be merged label May 1, 2026
hughcars added 2 commits May 4, 2026 11:58
icx in oneAPI 2026.0.0 rejects the GCC-specific -print-multi-os-directory
option that libffi 3.5.2's configure emits, breaking the Intel build.
Spack's new installer defers build-type deps when the parent's binary
comes from cache, which causes buildcache push to fail with
PackageNotInstalledError for 28 specs (bison, pigz, util-macros, ...).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-long-tests This PR does not require the long tests to be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant