Skip to content

ci(spack): pin buildcache geant4 to supported version#413

Merged
plexoos merged 1 commit into
mainfrom
fix-spack-build
Jul 11, 2026
Merged

ci(spack): pin buildcache geant4 to supported version#413
plexoos merged 1 commit into
mainfrom
fix-spack-build

Conversation

@plexoos

@plexoos plexoos commented Jul 11, 2026

Copy link
Copy Markdown
Member

The buildcache refresh failed while concretizing simphony with ^geant4@11.4.2 because the official spack/spack-packages Geant4 package metadata does not declare 11.4.2 yet.

Keep the Dockerfile default at 11.4.2 for the normal image builds, but pass GEANT4_VERSION=11.4.1 when this workflow builds the spack-base image. The container exports that value, so the subsequent spack spec/install commands use a version currently available to Spack.

References: https://github.com/BNLNPPS/simphony/actions/runs/29130246634/job/86484075917

The buildcache refresh failed while concretizing simphony with ^geant4@11.4.2 because the official spack/spack-packages Geant4 package metadata does not declare 11.4.2 yet.

Keep the Dockerfile default at 11.4.2 for the normal image builds, but pass GEANT4_VERSION=11.4.1 when this workflow builds the spack-base image. The container exports that value, so the subsequent spack spec/install commands use a version currently available to Spack.

References: https://github.com/BNLNPPS/simphony/actions/runs/29130246634/job/86484075917
Copilot AI review requested due to automatic review settings July 11, 2026 00:37

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the buildcache refresh GitHub Actions workflow to avoid Spack concretization failures caused by requesting a Geant4 version not yet declared in Spack’s package metadata, while keeping the repository’s Dockerfile default Geant4 version ahead for normal image builds.

Changes:

  • Passes GEANT4_VERSION=11.4.1 as a Docker build argument when building the spack-base image in the buildcache refresh workflow.
  • Documents (in-workflow) why the workflow pins Geant4 to a Spack-supported version even if the Dockerfile default moves ahead.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@plexoos plexoos self-assigned this Jul 11, 2026
@plexoos plexoos added ci build Build-system or toolchain configuration problems labels Jul 11, 2026
@plexoos plexoos merged commit 462cbd9 into main Jul 11, 2026
24 checks passed
@plexoos plexoos deleted the fix-spack-build branch July 11, 2026 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Build-system or toolchain configuration problems ci

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants