Skip to content

[PROTON] Migrate Proton ROCm backend from roctracer to rocprofiler-sdk #13198

[PROTON] Migrate Proton ROCm backend from roctracer to rocprofiler-sdk

[PROTON] Migrate Proton ROCm backend from roctracer to rocprofiler-sdk #13198

Triggered via pull request April 16, 2026 18:26
Status Cancelled
Total duration 3h 22m 8s
Artifacts

ci.yml

on: pull_request
runner-preparation  /  prepare
3s
runner-preparation / prepare
pre-commit  /  pre-commit (code formatting)
2m 5s
pre-commit / pre-commit (code formatting)
Matrix: build-macos / Build MacOS
Matrix: integration-tests-amd / integration-tests-amd
Matrix: integration-tests-nvidia / integration-tests-nvidia
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 9 warnings
build-macos / Build MacOS (macos-latest)
Process completed with exit code 2.
integration-tests-amd / integration-tests-amd (gfx950-rocm712)
Process completed with exit code 2.
integration-tests-amd / integration-tests-amd (gfx90a)
Process completed with exit code 2.
integration-tests-amd / integration-tests-amd (gfx942)
Process completed with exit code 2.
integration-tests-nvidia / integration-tests-nvidia (nvidia-a100)
Canceling since a higher priority waiting request for refs/pull/9704/merge exists
Integration Tests
Canceling since a higher priority waiting request for refs/pull/9704/merge exists
Integration Tests
Canceling since a higher priority waiting request for refs/pull/9704/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/
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 (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/
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/