[GSan] Model TMAReduceOp as atomic #13180
ci.yml
on: pull_request
runner-preparation
/
prepare
5s
pre-commit
/
pre-commit (code formatting)
1m 5s
Matrix: build-macos / Build MacOS
Matrix: integration-tests-amd / integration-tests-amd
Matrix: integration-tests-nvidia / integration-tests-nvidia
Annotations
15 errors and 10 warnings
|
integration-tests-nvidia / integration-tests-nvidia (nvidia-a100)
Process completed with exit code 2.
|
|
integration-tests-nvidia / integration-tests-nvidia (nvidia-h100)
The strategy configuration was canceled because "integration-tests-nvidia.integration-tests-nvidia.nvidia-a100_nvidia-a100_n" failed
|
|
integration-tests-nvidia / integration-tests-nvidia (nvidia-h100)
The operation was canceled.
|
|
integration-tests-nvidia / integration-tests-nvidia (nvidia-gb200)
The strategy configuration was canceled because "integration-tests-nvidia.integration-tests-nvidia.nvidia-a100_nvidia-a100_n" failed
|
|
integration-tests-nvidia / integration-tests-nvidia (nvidia-gb200)
The operation was canceled.
|
|
integration-tests-amd / integration-tests-amd (amd-gfx942)
Process completed with exit code 2.
|
|
integration-tests-amd / integration-tests-amd (amd-gfx950)
The strategy configuration was canceled because "integration-tests-amd.integration-tests-amd.amd-gfx942" failed
|
|
integration-tests-amd / integration-tests-amd (amd-gfx950)
The operation was canceled.
|
|
build-macos / Build MacOS (macos-latest)
Canceling since a higher priority waiting request for refs/pull/10053/merge exists
|
|
build-macos / Build MacOS (macos-latest)
Process completed with exit code 2.
|
|
integration-tests-amd / integration-tests-amd (self-hosted, gfx90a)
The strategy configuration was canceled because "integration-tests-amd.integration-tests-amd.amd-gfx942" failed
|
|
integration-tests-amd / integration-tests-amd (self-hosted, gfx90a)
The operation was canceled.
|
|
Integration Tests
Canceling since a higher priority waiting request for refs/pull/10053/merge exists
|
|
Integration Tests
Canceling since a higher priority waiting request for refs/pull/10053/merge exists
|
|
Integration Tests
Canceling since a higher priority waiting request for refs/pull/10053/merge exists
|
|
runner-preparation / prepare
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
runner-preparation / prepare
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
runner-preparation / prepare
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
pre-commit / pre-commit (code formatting)
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 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/
|
|
integration-tests-nvidia / integration-tests-nvidia (nvidia-a100)
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 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/
|
|
integration-tests-nvidia / integration-tests-nvidia (nvidia-h100)
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 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/
|
|
integration-tests-nvidia / integration-tests-nvidia (nvidia-gb200)
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 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/
|
|
build-macos / Build MacOS (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache@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/
|
|
build-macos / Build MacOS (macos-latest)
llvm@19 was installed but not linked because llvm@18 is already installed.
To link this version, run:
brew link llvm@19
|
|
integration-tests-amd / integration-tests-amd (self-hosted, gfx90a)
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 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/
|