-
Notifications
You must be signed in to change notification settings - Fork 55
Automated testing and building
Rick Grubin edited this page Apr 16, 2025
·
7 revisions
| Platform name | Maintaining org. | Job system (Jenkins, cron, etc.) | Key applications to test | Notes |
|---|---|---|---|---|
| Acorn | EMC | cron | UFS WM | builds as user (no role account) |
| Orion | EPIC | Jenkins | UFS WM | role.epic account |
| ... | ... | ... | ... | ... |
| Package | Has Spack-accessible unit tests | Work needed (link to issues) |
|---|---|---|
| bacio | yes | version upgrade for unit testing |
| g2 | yes | none |
| g2c | yes | none |
| jasper | yes | none |
| libaec | yes | none |
| libpng | yes | none |
| scotch | yes | none |
| w3emc | yes | none |
| hdf5 | yes | Set HDF5_TEST_PARALLEL through Spack[1] |
| ip | yes | https://github.com/NOAA-EMC/NCEPLIBS-ip/issues/250 |
1: May be needed for systems where testing with MPI is inconvenient. Alternatively, maybe HDF5 can be modified to support job schedulers.
Note that spack install --test does not fail if a package has no make test or make check targets. Therefore it is strongly recommended that each package recipe override Spack's built-in check() function so as to ensure that unit tests must successfully run:
def check(self):
with working_dir(self.builder.build_directory):
make("test")