Skip to content

Fix GPU MPI coords device pointer bug #355

Fix GPU MPI coords device pointer bug

Fix GPU MPI coords device pointer bug #355

Re-run triggered March 16, 2026 11:55
Status Failure
Total duration 1m 46s
Artifacts
Matrix: Release Build and Test
Debug Build and Test
1m 34s
Debug Build and Test
macOS Build and Test
56s
macOS Build and Test
Matrix: NVIDIA Build (No Test)
Build as Subproject
0s
Build as Subproject
CMake Discovery
0s
CMake Discovery
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 9 warnings
macOS Build and Test
Process completed with exit code 2.
Release Build and Test (gnu, 12, OFF, ON)
Process completed with exit code 1.
Release Build and Test (gnu, 12, OFF, OFF)
The strategy configuration was canceled because "release_build.gnu_12_OFF_ON" failed
Release Build and Test (gnu, 12, OFF, OFF)
Process completed with exit code 1.
Release Build and Test (gnu, 12, ON, ON)
The strategy configuration was canceled because "release_build.gnu_12_OFF_ON" failed
Release Build and Test (gnu, 12, ON, ON)
The operation was canceled.
Debug Build and Test
Process completed with exit code 1.
Release Build and Test (llvm, 19, ON, OFF)
The strategy configuration was canceled because "release_build.gnu_12_OFF_ON" failed
Release Build and Test (llvm, 19, ON, OFF)
The operation was canceled.
Release Build and Test (llvm, 19, OFF, OFF)
The strategy configuration was canceled because "release_build.gnu_12_OFF_ON" failed
Release Build and Test (llvm, 19, OFF, OFF)
The operation was canceled.
Release Build and Test (gnu, 12, ON, OFF)
The strategy configuration was canceled because "release_build.gnu_12_OFF_ON" failed
Release Build and Test (gnu, 12, ON, OFF)
The operation was canceled.
NVIDIA Build (No Test) (ON, OFF)
Process completed with exit code 1.
NVIDIA Build (No Test) (OFF, ON)
The strategy configuration was canceled because "nvidia_build.ON_OFF" failed
NVIDIA Build (No Test) (OFF, ON)
The operation was canceled.
NVIDIA Build (No Test) (OFF, OFF)
The strategy configuration was canceled because "nvidia_build.ON_OFF" failed
NVIDIA Build (No Test) (OFF, OFF)
The operation was canceled.
macOS Build and Test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, mamba-org/setup-micromamba@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
Release Build and Test (gnu, 12, OFF, ON)
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. 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/
Release Build and Test (gnu, 12, OFF, OFF)
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. 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/
Release Build and Test (gnu, 12, ON, ON)
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. 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/
Debug Build and Test
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. 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/
Release Build and Test (llvm, 19, ON, OFF)
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. 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/
Release Build and Test (llvm, 19, OFF, OFF)
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. 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/
Release Build and Test (gnu, 12, ON, OFF)
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. 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/
NVIDIA Build (No Test) (ON, OFF)
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. 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/