Skip to content

Conversation

@mcfadden8
Copy link
Collaborator

Not ready to place this into the spack1.0.2 branch yet, but I wanted to kick CI to see if the progress made has helped any with github CI.

mcfadden8 and others added 30 commits October 27, 2025 08:14
Replace obsolete "spack concretize -U" with
spack:concretizer:reuse:false to disable it by default within our
build environment.

Move compiler definitions from compilers.yaml to packages.yaml since
compilers.yaml is obsolete in v1.0

Update specs to handle new semantics for "%" in v1.0

Updated using packages to point to new, separate package repository
for spack.

Added "depends_on" for package language dependencies (c, cxx,
fortran)

Renamed "m-aneos" package to "m_aneos" to match new package naming
requirements of spack v1.0
…, added c and cxx dependencies for packages missing them, added fortran dependency to spheral to avoid known spack bug, python concretize function is called instead of SpackCommand
…t docker failure, add permissions to spack config, removed tpl permissions stage since that is done by tpl-manager now
ldowen and others added 30 commits November 21, 2025 12:03
Updated package directory names and spec name to
follow spack v1.1 naming requirements
…added environment variable settings for the llvm-amdgpu package recipe
…ed the c, cxx, and fortran depends_on below variants in package recipe, added ~fortran variant to silo
to work.

Also, removed packages that are no longer necessary since their
versions are now in the spack builtins.
Python 3.12 introduced breaking changes that caused test failures:

1. unittest test discovery: Changed timing/caching of test method
   discovery. Deleting methods from base classes after import no
   longer prevents discovery in subclasses. Fixed by explicitly
   replacing unwanted test methods with @unittest.skip decorated
   versions on each test class.

2. Enum string representation: str(enum_value) changed from
   "EnumClass.MEMBER" in 3.9 to the integer value in 3.12. This
   caused reference file path mismatches in TensileRod tests. Fixed
   by explicitly constructing enum names using __class__.__name__
   and .name attributes for consistent behavior across versions.

Both fixes maintain backward compatibility with Python 3.9.

Modified files:
- tests/unit/Neighbor/testNestedGridNeighbor.py
- tests/functional/Damage/TensileRod/TensileRod-1d.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants