Skip to content

Add HDF5 2.2.0 container image and CI workflow - #166

Open
jeanbez wants to merge 1 commit into
developfrom
hdf5-2.2.0-ci
Open

Add HDF5 2.2.0 container image and CI workflow#166
jeanbez wants to merge 1 commit into
developfrom
hdf5-2.2.0-ci

Conversation

@jeanbez

@jeanbez jeanbez commented Jul 30, 2026

Copy link
Copy Markdown
Member

Adds a HDF5 2.2.0 image and matching CI job, mirroring the 2.0.0 and 2.1.1 setups.

Summary

  • `docker/ubuntu-24.04-hdf5-2.2.0/Dockerfile`: Ubuntu 24.04, HDF5 2.2.0 from the GitHub release tarball, same flags as the other 2.x images.
  • `.github/workflows/h5bench-hdf5-2.2.0.yml`: consumes `hpcio/hdf5-2.2.0`, runs the full SYNC + ASYNC suite.

Prerequisite

The image must be built and pushed to `hpcio/hdf5-2.2.0` for the workflow to pass. Build for linux/amd64 explicitly if pushing from an Apple Silicon Mac:

```
docker buildx build --platform linux/amd64 \
-t hpcio/hdf5-2.2.0 docker/ubuntu-24.04-hdf5-2.2.0 --push
```

Test plan

  • Build the Docker image locally with the linux/amd64 platform pin.
  • Push to `hpcio/hdf5-2.2.0`.
  • Confirm the new workflow goes green on this PR.

@codecov

codecov Bot commented Jul 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.85%. Comparing base (94f11ed) to head (0d4279e).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #166   +/-   ##
========================================
  Coverage    58.85%   58.85%           
========================================
  Files           14       14           
  Lines         6062     6062           
  Branches      1427     1427           
========================================
  Hits          3568     3568           
  Misses        1917     1917           
  Partials       577      577           
Flag Coverage Δ
c 58.85% <ø> (ø)
python 58.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

jeanbez added a commit that referenced this pull request Aug 12, 2026
Wave D item 18, minimal-scope variant. The five workflow files that
run the identical SYNC+ASYNC suite against different HDF5 versions
(1.14.0, 1.14.1, 2.0.0, 2.1.1, 2.2.0) collapse into a single matrix
workflow. The four older SYNC-only files (1.10.4, 1.10.7, 1.10.8,
1.12.0) stay as-is because their test set is a strict subset and
they don't run the ASYNC leg; collapsing them would require
conditional gates that make the matrix noisier than the win.

## New file

.github/workflows/h5bench-hdf5-matrix.yml
  - strategy.fail-fast: false so one bad version does not cancel
    the others
  - strategy.matrix.hdf5_version: [1.14.0, 1.14.1, 2.0.0, 2.1.1, 2.2.0]
  - container.image: hpcio/hdf5-${{ matrix.hdf5_version }}
  - job name: "h5bench (HDF5 ${{ matrix.hdf5_version }})" so each
    matrix leg reports as e.g. "h5bench (HDF5 2.0.0)", matching the
    old per-version workflow's job name as closely as possible.

## Deleted

.github/workflows/h5bench-hdf5-1.14.0.yml
.github/workflows/h5bench-hdf5-1.14.1.yml
.github/workflows/h5bench-hdf5-2.0.0.yml
.github/workflows/h5bench-hdf5-2.1.1.yml

## Branch protection

Required-check names WILL shift. The old checks appeared as
"h5bench (HDF5 X.X.X) / h5bench"; the new ones appear as
"h5bench / h5bench (HDF5 X.X.X)". Any required-check rules on
develop/master that name the old paths must be updated before
this merges, or the required checks will hang.

## Coordination with #166 (2.2.0)

If #166 lands first, its h5bench-hdf5-2.2.0.yml must be deleted on
rebase of this PR (it is redundant with the matrix leg). If this PR
lands first, #166 should drop the per-version file and just push the
image.
Mirrors the 2.0.0 and 2.1.1 setups. New ubuntu-24.04-hdf5-2.2.0
Dockerfile based on Ubuntu 24.04, building HDF5 2.2.0 from the GitHub
release tarball with the same parallel + threadsafe +
allow-unsupported flags. New h5bench-hdf5-2.2.0.yml workflow consumes
hpcio/hdf5-2.2.0 and runs the same SYNC + ASYNC suite as 2.0.0 and
2.1.1.

The image needs to be built and pushed to hpcio/hdf5-2.2.0 before the
workflow can go green:

  docker buildx build --platform linux/amd64 \\
    -t hpcio/hdf5-2.2.0 docker/ubuntu-24.04-hdf5-2.2.0 --push
@jeanbez
jeanbez marked this pull request as ready for review August 22, 2026 00:03
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.

1 participant