fix problem with fill values for very large compound and vlen types #460
docker_regression_testing.yml
on: pull_request
Matrix: Docker-Based NetCDF-C, Fortran Regression Testing (Serial)
Matrix: Docker-Based NetCDF-C and Fortran Regression Testing, S3 (Internal) and Zarr (Serial)
Matrix: Docker-Based NetCDF-C, Fortran Regression Testing (tinyxml2-related one-off tests)
Matrix: Docker-Based NetCDF-C, Fortran Regression Testing (Parallel)
Matrix: Docker-Based NetCDF-C, Java Regression Testing (Serial, Java Only)
Annotations
16 errors and 11 warnings
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.14.6, v4.6.2, both)
The strategy configuration was canceled because "netcdf-test-matrix-serial.c_clang_1_14_6_v4_6_2_bot" failed
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.14.6, v4.6.2, both)
The operation was canceled.
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.12.1, main, both)
The strategy configuration was canceled because "netcdf-test-matrix-serial.c_clang_1_14_6_v4_6_2_bot" failed
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.12.1, main, both)
The operation was canceled.
|
|
Docker-Based NetCDF-C and Fortran Regression Testing, S3 (Internal) and Zarr (Serial) (c, clang, ...
The strategy configuration was canceled because "netcdf-tests-s3-serial.c_gcc_1_14_6_main_both" failed
|
|
Docker-Based NetCDF-C and Fortran Regression Testing, S3 (Internal) and Zarr (Serial) (c, clang, ...
The operation was canceled.
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.12.1, main, both)
The strategy configuration was canceled because "netcdf-test-matrix-serial.c_clang_1_14_6_v4_6_2_bot" failed
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.12.1, main, both)
The operation was canceled.
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.14.6, main, both)
The strategy configuration was canceled because "netcdf-test-matrix-serial.c_clang_1_14_6_v4_6_2_bot" failed
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.14.6, main, both)
The operation was canceled.
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.12.1, v4.6.2, both)
The strategy configuration was canceled because "netcdf-test-matrix-serial.c_clang_1_14_6_v4_6_2_bot" failed
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.12.1, v4.6.2, both)
The operation was canceled.
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.12.1, v4.6.2, both)
The strategy configuration was canceled because "netcdf-test-matrix-serial.c_clang_1_14_6_v4_6_2_bot" failed
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.12.1, v4.6.2, both)
The operation was canceled.
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.14.6, main, both)
The strategy configuration was canceled because "netcdf-test-matrix-serial.c_clang_1_14_6_v4_6_2_bot" failed
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.14.6, main, both)
The operation was canceled.
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.14.6, v4.6.2, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C and Fortran Regression Testing, S3 (Internal) and Zarr (Serial) (c, gcc, 1....
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.12.1, main, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C and Fortran Regression Testing, S3 (Internal) and Zarr (Serial) (c, clang, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.12.1, main, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.14.6, main, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.12.1, v4.6.2, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.12.1, v4.6.2, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, gcc, 1.14.6, main, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.14.6, v4.6.2, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Docker-Based NetCDF-C, Fortran Regression Testing (Serial) (c, clang, 1.14.6, v4.6.2, both)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|