3 Test Failures with MinGW Static GCC Configuration (HDF5_MINGW_STATIC_GCC_LIBS=ON)

[hyoklee]

Description

Three tests are failing when building HDF5 with the MinGW Static GCC configuration on Windows. The failures were detected in CDash build ID 3178953.

CDash Build Report: https://my.cdash.org/viewTest.php?onlyfailed&buildid=3178953

Failed Tests

1. H5TESTXPR-cache_api - Execution time: 40ms
2. H5TEST-dt_arith - Execution time: 250ms
3. H5TEST-err_compat - Execution time: 40ms

Build Configuration

The failures occurred with the following CMake configuration:

cmake -G Ninja \
  -DCMAKE_BUILD_TYPE=Release \
  -DHDF5_MINGW_STATIC_GCC_LIBS:BOOL=ON \
  -DBUILD_SHARED_LIBS:BOOL=ON \
  -DHDF5_BUILD_CPP_LIB:BOOL=ON \
  -DHDF5_BUILD_FORTRAN:BOOL=OFF \
  -DHDF5_BUILD_JAVA:BOOL=OFF \
  -DHDF5_BUILD_HL_LIB:BOOL=ON \
  -DHDF5_ENABLE_ZLIB_SUPPORT:BOOL=OFF \
  -DHDF5_ENABLE_SZIP_SUPPORT:BOOL=OFF

Environment

• Platform: Windows Server 2022 (Build 26100)
• Architecture: AMD64
• Compiler: MinGW-w64 GCC (D:/a/_temp/msys64/mingw64/bin/c++.exe)
• Build System: Ninja
• MSYS2 System: MINGW64
• Build Name: mw/cpp
• Site: win-22
• Test Time: 2025-11-04 19:29:49 UTC

Workflow

This configuration is tested via the GitHub Actions workflow: win_mgw_sta.yml

The key configuration flag being tested is:

• HDF5_MINGW_STATIC_GCC_LIBS:BOOL=ON - This enables static linking of GCC runtime libraries on MinGW

Additional Information

All three tests completed execution but failed their validation checks. The total test execution time was approximately 5 minutes 42 seconds for the entire test suite.

Expected Behavior

All tests should pass with the MinGW Static GCC configuration, as this is a supported build configuration for HDF5 on Windows.

Reproduction

The issue can be reproduced by:

1. Setting up MSYS2 with MINGW64 environment
2. Installing mingw-w64-x86_64-gcc, mingw-w64-x86_64-cmake, mingw-w64-x86_64-ninja
3. Configuring HDF5 with the CMake flags listed above
4. Running ctest -D Experimental

[byrnHDF]

Yes those tests are expected to fail, see the MSYS2 workflows.

[lrknox]

Msys2 Workflows / 🟦 MSYS2-mingw64-Release runs this configuration, expecting 5 tests to fail including these three. testhdf5-base and dtypes tests are now passing and will be moved in to the tests expected to pass in the workflow.