Files
hdf5/.github/workflows/java-implementation-test.yml
T
Workflow config file is invalid. Please check your config file: getMatrixes: matrix include must be a list of mappings
cde84cdc8f Update hdf5 2.1.0 with 17commits from develop since 2/5/2026 (#6229)
* Fix MPI Fortran configuration for HDF5Examples (#6206)

When building Fortran parallel examples without MPI wrappers, the
compiler couldn't find mpi.mod because MPI_Fortran_INCLUDE_DIRS
was not populated. This occurred because find_package(MPI) was only
called for C, not Fortran.

Added enable_language(Fortran) and find_package(MPI REQUIRED
COMPONENTS Fortran) to properly configure MPI for Fortran examples,
ensuring MPI include directories and libraries are correctly set.

* Adds RFCs to the RFC table (#6190)

* Added two RFCs to the RFC table

"Adding support for digitally signed plugins to HDF5"
" Write-Ahead log"

* Updated to use the ACM link

* Add HDF5 2.0.0 Library Migration Guide (#6183)

* Add HDF5 2.0.0 Library Migration Guide

* Revise HDF5 migration guide for version 2.0.0

Use 2.0.0 consistently.

* Clarify API changes in HDF5 2.0.0 Migration Guide

* Fixes the "multiple @param documentation sections" doxygen warnings (#6195)

Addresses the "multiple @ param documentation sections" warnings are caused by the interaction of three things:

1. MACRO_EXPANSION = YES with EXPAND_ONLY_PREDEF = NO in Doxyfile.in

2. Versioned API macros in H5version.h like:

\def documentation in APIVersions.dox like:

3. \def H5Tarray_create \api_vers_2{H5Tarray_create,H5Tarray_create1,H5Tarray_create2}

Because Doxygen expands all macros, it sees H5Tarray_create as an alias for H5Tarray_create1. It then associates documentation from both the \def block (for the macro) and the function's own doc block (with \param entries) with the same function — resulting in "multiple @ param documentation sections."

* Update Doxygen version from 1.16.0 to 1.16.1

Use Doxygen 1.16.1 for all platforms. This version includes the latest
bug fixes and improvements while maintaining compatibility with our
documentation format.

* Fix Windows Doxygen installation for version 1.16.1

Handle different Windows binary naming conventions across Doxygen versions:
- 1.16.1 uses: doxygen-VERSION.windows.x64.bin.zip
- 1.16.0 uses: doxygen-VERSION.x64.bin.zip

Try the newer naming convention first, then fall back to the older one
if the download fails. This ensures compatibility across versions.

* Use ssciwr/doxygen-install in setup-doxygen action

Replace direct installation of official Doxygen binaries with
ssciwr/doxygen-install action. This avoids Java documentation parsing
errors that occur with official binaries but not with distribution
builds.

The setup-doxygen action now serves as a thin wrapper around
ssciwr/doxygen-install@f13be16c83 (v1),
using commit hash for security and reproducibility.

* Remove redundant version specification from workflows

The setup-doxygen action already has a default version (1.16.1),
so explicit version specification in workflows is unnecessary.
This follows DRY principles and makes version updates simpler.

* Updates to #6205 (#6208)

* Fix MPI Fortran configuration for HDF5Examples (#6205)

When building Fortran parallel examples standalone without MPI
wrappers, the compiler cannot find mpi.mod because
MPI_Fortran_INCLUDE_DIRS is not populated.

* Use MPI::MPI_Fortran imported target instead of raw MPI variables

Replace manual MPI_Fortran_LIBRARIES, MPI_Fortran_LINK_FLAGS, and
MPI_Fortran_INCLUDE_DIRS usage with the MPI::MPI_Fortran imported
target, which transitively carries all include dirs, compile flags,
and link flags. This eliminates the CMAKE_Fortran_EXE_LINKER_FLAGS
hack and the manual target_include_directories in H5PAR.

* Update nvhpc version to 26.1 with CUDA version 13.1. (#6213)

# branches: [develop]

* Inherit Debug C build flags in Developer build mode (#6182)

* Bump the github-actions group across 1 directory with 11 updates (#6215)

* Bump the github-actions group across 1 directory with 11 updates

Bumps the github-actions group with 11 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [actions/cache](https://github.com/actions/cache) | `5.0.1` | `5.0.3` |
| [lukka/get-cmake](https://github.com/lukka/get-cmake) | `4.2.1` | `4.2.3` |
| [softwareforgood/check-artifact-v4-existence](https://github.com/softwareforgood/check-artifact-v4-existence) | `0.3.0` | `0.4.1` |
| [github/codeql-action](https://github.com/github/codeql-action) | `3.31.9` | `4.32.2` |
| [azure/trusted-signing-action](https://github.com/azure/trusted-signing-action) | `0.5.11` | `1.1.0` |
| [cygwin/cygwin-install-action](https://github.com/cygwin/cygwin-install-action) | `7d2dc1e241644c3318bed9ec74115d1929baa681` | `2566376092c4e280f21131be027af3f5bb2420a4` |
| [aws-actions/configure-aws-credentials](https://github.com/aws-actions/configure-aws-credentials) | `5.1.1` | `6.0.0` |
| [vmactions/freebsd-vm](https://github.com/vmactions/freebsd-vm) | `1.3.4` | `1.4.2` |
| [vmactions/openbsd-vm](https://github.com/vmactions/openbsd-vm) | `1.3.1` | `1.3.5` |
| [mpi4py/setup-mpi](https://github.com/mpi4py/setup-mpi) | `1.4.1` | `1.4.2` |
| [actions/setup-python](https://github.com/actions/setup-python) | `6.1.0` | `6.2.0` |

 vmactions/openbsd-vm@d6c29ce1b4 (`1.3.5`) failed to run ssh on the github runner.  271a1ba62300483cfc58345ff9f425f1349a2cab for v1.3.4 was used instead.

* Fix issue with some Subfiling VFD test files not getting deleted (#6212)

* CMake: Fix Fortran cross-compilation support

Refactor the cross-compilation infrastructure to rely on the standard
CMAKE_CROSSCOMPILING_EMULATOR variable instead of the custom
CROSSCOMPILING_PATH environment hack.

Key changes:
- Removed `ENVIRONMENT "${CROSSCOMPILING_PATH}"` from all test definitions.
- Updated custom commands (e.g., H5match_types, H5_gen) to invoke the
  emulator explicitly when cross-compiling.
- Updated ConfigureChecks.cmake and HDF5UseFortran.cmake to enable
  `try_run` checks when an emulator is defined.
- Added config/toolchain/mingw-w64-x86-64-wine.sh wrapper to automatically
  locate MinGW runtime libraries (like libgfortran) for Wine execution.
- Cleaned up toolchain files to remove hardcoded emulator paths, deferring
  configuration to the build environment.

* Add Doxygen setup that results in missing Doygen documentation. (#6217)

* Added setup-doxygen action in ctest.yml Ubuntu gcc workflow.
* Also added actions/checkout for setup-doxygen.

* Fixes link checker failure (#6219)

Removed https:// as a workaround to avoid error by the link checker.

* Remove force-setting of ZLIB_USE_EXTERNAL / SZIP_USE_EXTERNAL (#6222)

Removes the force-setting of ZLIB_USE_EXTERNAL and SZIP_USE_EXTERNAL to
ON when HDF5_ALLOW_EXTERNAL_SUPPORT is GIT or TGZ so that zlib and
szip can be independently built from the system or externally as desired

* Truncate Subfiling VFD's stub file when truncating subfiles (#6210)

Ensure that the Subfiling VFD's stub file gets truncated when subfiles are
being truncated to avoid a potentially unreadable file when the EOF doesn't
match the stored EOF value

Co-authored-by: Larry Knox <lrknox@hdfgroup.org>

* Add CMake function to extract pkg-config info from libraries (#6220)

* Consistent extension for C++ (#6214)

Except for this file, all use cpp instead of cxx. No obvious reason why
the same file types should have different extensions.

* Enable Windows ARM64 CTest CI for release binaries (#6177)

* ci: add Windows ARM64 MSVC CTest job

* ci: add MSYS2 clangarm64 build on Windows ARM64

* cmake: add MSVC ARM64 presets for Windows

* zlib: fix MSVC static library flags for ARM64 builds

* Renamed .hxx file to .h and updated the #include for it.

* Committing clang-format changes

---------

Co-authored-by: Scot Breitenfeld <brtnfld@hdfgroup.org>
Co-authored-by: bmribler <39579120+bmribler@users.noreply.github.com>
Co-authored-by: Gerd Heber <gheber@hdfgroup.org>
Co-authored-by: jhendersonHDF <jhenderson@hdfgroup.org>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Julien Schueller <schueller@phimeca.com>
Co-authored-by: Martin Diehl <mail@martin-diehl.net>
Co-authored-by: Harish RS <harish.rajaselvan@multicorewareinc.com>
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
2026-02-20 17:03:09 -06:00

318 lines
11 KiB
YAML

name: Java Implementation Testing (FFM vs JNI)
# Test both FFM and JNI implementations across multiple Java versions
on:
pull_request:
branches: [ develop, main ]
paths:
- 'java/**'
- 'CMakeBuildOptions.cmake'
- 'CMakePresets.json'
- 'config/cmake-presets/hidden-presets.json'
- '.github/workflows/java-implementation-test.yml'
- '.github/scripts/test-java-implementations.sh'
workflow_call:
inputs:
java_versions:
description: 'Java versions to test (comma-separated)'
type: string
required: false
default: '11,17,21,24'
test_mode:
description: 'Test mode (build, maven, full)'
type: string
required: false
default: 'build'
platforms:
description: 'Platforms to test'
type: string
required: false
default: 'ubuntu-latest'
workflow_dispatch:
inputs:
java_versions:
description: 'Java versions to test'
type: string
required: false
default: '11,17,21,24'
test_mode:
description: 'Test mode'
type: choice
required: false
default: 'build'
options:
- 'build'
- 'maven'
- 'full'
platforms:
description: 'Platforms to test'
type: choice
required: false
default: 'ubuntu-latest'
options:
- 'ubuntu-latest'
- 'windows-latest'
- 'macos-latest'
- 'all-platforms'
env:
CMAKE_GENERATOR: Ninja
jobs:
setup-matrix:
runs-on: ubuntu-latest
outputs:
matrix: ${{ steps.generate-matrix.outputs.matrix }}
steps:
- name: Generate test matrix
id: generate-matrix
run: |
# Parse inputs
JAVA_VERSIONS="${{ inputs.java_versions || '11,17,21,25' }}"
PLATFORMS="${{ inputs.platforms || 'ubuntu-latest' }}"
# Expand platforms if needed
if [[ "$PLATFORMS" == "all-platforms" ]]; then
PLATFORMS="ubuntu-latest,windows-latest,macos-latest"
fi
# Generate matrix
matrix_json="["
first_entry=true
for platform in $(echo "$PLATFORMS" | tr ',' ' '); do
for java_version in $(echo "$JAVA_VERSIONS" | tr ',' ' '); do
# Determine available implementations
if [[ $java_version -ge 25 ]]; then
implementations="ffm jni"
else
implementations="jni"
fi
for impl in $implementations; do
if [ "$first_entry" = true ]; then
first_entry=false
else
matrix_json="$matrix_json,"
fi
matrix_json="$matrix_json{\"os\":\"$platform\",\"java-version\":\"$java_version\",\"implementation\":\"$impl\"}"
done
done
done
matrix_json="$matrix_json]"
echo "Generated matrix:"
echo "$matrix_json" | jq '.'
echo "matrix=$matrix_json" >> $GITHUB_OUTPUT
test-implementations:
needs: setup-matrix
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
include: ${{ fromJson(needs.setup-matrix.outputs.matrix) }}
name: Test Java ${{ matrix.java-version }} ${{ matrix.implementation }} on ${{ matrix.os }}
steps:
- name: Checkout repository
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
with:
submodules: recursive
- name: Set up Java ${{ matrix.java-version }} (${{ matrix.implementation }})
uses: actions/setup-java@f2beeb24e141e01a676f977032f5a29d81c9e27e # v5
with:
distribution: ${{ matrix.implementation == 'ffm' && 'oracle' || 'temurin' }}
java-version: ${{ matrix.implementation == 'ffm' && '25' || matrix.java-version }}
- name: Setup jextract (FFM builds only)
if: ${{ matrix.implementation == 'ffm' }}
uses: ./.github/actions/setup-jextract
with:
java-version: '25'
- name: Setup Build Environment (Linux)
if: runner.os == 'Linux'
run: |
sudo apt-get update
sudo apt-get install -y ninja-build libaec-dev zlib1g-dev
- name: Setup Build Environment (macOS)
if: runner.os == 'macOS'
run: |
brew install ninja libaec
- name: Setup Build Environment (Windows)
if: runner.os == 'Windows'
run: |
choco install ninja
- name: Cache CMake build
uses: actions/cache@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v4
with:
path: |
build-test-*
key: ${{ runner.os }}-java${{ matrix.java-version }}-${{ matrix.implementation }}-${{ hashFiles('**/CMakeLists.txt', 'CMakePresets.json') }}
restore-keys: |
${{ runner.os }}-java${{ matrix.java-version }}-${{ matrix.implementation }}-
${{ runner.os }}-java${{ matrix.java-version }}-
- name: Verify Java version and implementation compatibility
run: |
java -version
echo "Testing Java ${{ matrix.java-version }} with ${{ matrix.implementation }} implementation"
# Additional validation for FFM
if [[ "${{ matrix.implementation }}" == "ffm" ]]; then
if [[ ${{ matrix.java-version }} -lt 25 ]]; then
echo "::error::FFM implementation requires Java 25, got Java ${{ matrix.java-version }}"
exit 1
fi
echo "FFM implementation validated for Java ${{ matrix.java-version }}"
fi
- name: Run implementation tests
shell: bash
run: |
chmod +x .github/scripts/test-java-implementations.sh
.github/scripts/test-java-implementations.sh \
${{ matrix.java-version }} \
${{ matrix.implementation }} \
${{ inputs.test_mode || 'build' }}
- name: Upload build artifacts on failure
if: failure()
uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v5
with:
name: build-logs-${{ matrix.os }}-java${{ matrix.java-version }}-${{ matrix.implementation }}
path: |
build-test-*/CMakeCache.txt
build-test-*/CMakeFiles/CMakeError.log
build-test-*/CMakeFiles/CMakeOutput.log
retention-days: 7
- name: Upload Maven artifacts (if generated)
if: inputs.test_mode == 'maven' || inputs.test_mode == 'full'
uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v5
with:
name: maven-artifacts-${{ matrix.os }}-java${{ matrix.java-version }}-${{ matrix.implementation }}
path: |
build-test-*/java/**/target/*.jar
build-test-*/java/**/pom.xml
retention-days: 3
validate-artifacts:
needs: [setup-matrix, test-implementations]
runs-on: ubuntu-latest
if: inputs.test_mode == 'maven' || inputs.test_mode == 'full'
steps:
- name: Checkout repository
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
- name: Download all Maven artifacts
uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7.0.0
with:
pattern: maven-artifacts-*
path: artifacts/
- name: Validate artifact differentiation
run: |
echo "Validating Maven artifact differentiation..."
# Check for FFM artifacts
ffm_artifacts=$(find artifacts/ -name "*hdf5-java-ffm*" | wc -l)
jni_artifacts=$(find artifacts/ -name "*hdf5-java-jni*" | wc -l)
echo "Found $ffm_artifacts FFM artifacts and $jni_artifacts JNI artifacts"
if [[ $ffm_artifacts -eq 0 && $jni_artifacts -eq 0 ]]; then
echo "::error::No Maven artifacts found!"
exit 1
fi
# Verify no mixed artifacts
mixed_artifacts=$(find artifacts/ -name "*hdf5-java-*" | grep -v -E "(ffm|jni)" | wc -l)
if [[ $mixed_artifacts -gt 0 ]]; then
echo "::error::Found artifacts without proper FFM/JNI differentiation"
find artifacts/ -name "*hdf5-java-*" | grep -v -E "(ffm|jni)"
exit 1
fi
echo "✅ Artifact differentiation validation passed"
- name: Validate POM files
run: |
echo "Validating POM file contents..."
for pom in $(find artifacts/ -name "pom.xml"); do
echo "Checking POM: $pom"
# Extract artifact ID
artifact_id=$(grep -o '<artifactId>hdf5-java-[^<]*</artifactId>' "$pom" | sed 's/<[^>]*>//g')
echo "Artifact ID: $artifact_id"
# Validate implementation metadata
if grep -q "hdf5-java-ffm" "$pom"; then
if ! grep -q "FFM" "$pom"; then
echo "::error::FFM POM missing implementation metadata"
exit 1
fi
echo "✅ FFM POM validation passed"
elif grep -q "hdf5-java-jni" "$pom"; then
if ! grep -q "JNI" "$pom"; then
echo "::error::JNI POM missing implementation metadata"
exit 1
fi
echo "✅ JNI POM validation passed"
else
echo "::error::POM has unrecognized artifact ID: $artifact_id"
exit 1
fi
done
report-results:
needs: [setup-matrix, test-implementations, validate-artifacts]
runs-on: ubuntu-latest
if: always()
steps:
- name: Generate test report
run: |
echo "## Java Implementation Test Results" >> $GITHUB_STEP_SUMMARY
echo "" >> $GITHUB_STEP_SUMMARY
echo "### Test Configuration" >> $GITHUB_STEP_SUMMARY
echo "- **Java Versions**: ${{ inputs.java_versions || '11,17,21,25' }}" >> $GITHUB_STEP_SUMMARY
echo "- **Test Mode**: ${{ inputs.test_mode || 'build' }}" >> $GITHUB_STEP_SUMMARY
echo "- **Platforms**: ${{ inputs.platforms || 'ubuntu-latest' }}" >> $GITHUB_STEP_SUMMARY
echo "" >> $GITHUB_STEP_SUMMARY
# Report job statuses
if [[ "${{ needs.test-implementations.result }}" == "success" ]]; then
echo "✅ **Implementation Tests**: PASSED" >> $GITHUB_STEP_SUMMARY
else
echo "❌ **Implementation Tests**: FAILED" >> $GITHUB_STEP_SUMMARY
fi
if [[ "${{ needs.validate-artifacts.result }}" == "success" ]]; then
echo "✅ **Artifact Validation**: PASSED" >> $GITHUB_STEP_SUMMARY
elif [[ "${{ needs.validate-artifacts.result }}" == "skipped" ]]; then
echo "⏭️ **Artifact Validation**: SKIPPED" >> $GITHUB_STEP_SUMMARY
else
echo "❌ **Artifact Validation**: FAILED" >> $GITHUB_STEP_SUMMARY
fi
echo "" >> $GITHUB_STEP_SUMMARY
echo "### Implementation Matrix" >> $GITHUB_STEP_SUMMARY
echo "| Java Version | FFM Support | JNI Support |" >> $GITHUB_STEP_SUMMARY
echo "|--------------|-------------|-------------|" >> $GITHUB_STEP_SUMMARY
echo "| 11 | ❌ | ✅ |" >> $GITHUB_STEP_SUMMARY
echo "| 17 | ❌ | ✅ |" >> $GITHUB_STEP_SUMMARY
echo "| 21 | ❌ | ✅ |" >> $GITHUB_STEP_SUMMARY
echo "| 24+ | ✅ (optional) | ✅ (default) |" >> $GITHUB_STEP_SUMMARY