Skip to content

Remove duplicate user fusion config and Clean up stale imports #32967

Remove duplicate user fusion config and Clean up stale imports

Remove duplicate user fusion config and Clean up stale imports #32967

Triggered via pull request May 12, 2026 08:27
Status Cancelled
Total duration 4m 30s
Artifacts

build-presets.yml

on: pull_request
Matrix: apple
Matrix: linux
Matrix: windows
Matrix: zephyr
Fit to window
Zoom out
Zoom in

Annotations

46 errors and 13 warnings
windows (pybind) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
windows (windows) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
apple (ios) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
apple (ios) / build
The operation was canceled.
apple (ios-simulator) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
apple (ios-simulator) / build
The operation was canceled.
apple (macos) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
apple (macos) / build
The operation was canceled.
apple (pybind) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
apple (pybind) / build
The operation was canceled.
apple (llm) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
apple (llm) / build
The operation was canceled.
apple (profiling) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
apple (profiling) / build
The operation was canceled.
linux (linux, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
linux (linux, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/ec2-user/actions-runner/_work/executorch/executorch/pytorch/executorch'. No such file or directory
linux (llm, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
linux (llm, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build
An error occurred trying to start process '/usr/bin/bash' with working directory '/home/ec2-user/actions-runner/_work/executorch/executorch/pytorch/executorch'. No such file or directory
linux (pybind, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
zephyr (zephyr) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
zephyr (zephyr) / build
The operation was canceled.
linux (linux, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
linux (linux, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
The operation was canceled.
linux (pybind, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
linux (pybind, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
The operation was canceled.
linux (llm, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
linux (llm, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
The operation was canceled.
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
Build Presets
Canceling since a higher priority waiting request for Build Presets-19507-false-false exists
apple (ios) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
apple (ios-simulator) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
apple (macos) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
apple (pybind) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
apple (llm) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
apple (profiling) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
linux (linux, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
linux (llm, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
linux (pybind, linux.arm64.2xlarge, executorch-ubuntu-22.04-gcc11-aarch64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./test-infra/.github/actions/setup-ssh, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
zephyr (zephyr) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./test-infra/.github/actions/setup-ssh, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
linux (linux, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./test-infra/.github/actions/setup-ssh, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
linux (pybind, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./test-infra/.github/actions/setup-ssh, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/
linux (llm, linux.2xlarge, executorch-ubuntu-22.04-clang12) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./test-infra/.github/actions/setup-ssh, actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683, pmeier/pytest-results-action@a2c1430e2bddadbad9f49a6f9b879f062c6b19b1. 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/