/var/lib/jenkins/workspace/aten/src/ATen/native/xnnpack/ChannelShuffle.cpp: In function ‘at::Tensor at::native::xnnpack::channel_shuffle(const at::Tensor&, int64_t)’:
/var/lib/jenkins/workspace/aten/src/ATen/native/xnnpack/ChannelShuffle.cpp:64:36: error: ‘xnn_create_channel_shuffle_nc_x32’ was not declared in this scope
   64 |   const xnn_status create_status = xnn_create_channel_shuffle_nc_x32(
      |                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/jenkins/workspace/aten/src/ATen/native/xnnpack/ChannelShuffle.cpp:82:37: error: ‘xnn_reshape_channel_shuffle_nc_x32’ was not declared in this scope; did you mean ‘xnn_reshape_transpose_nd_x32’?
   82 |   const xnn_status reshape_status = xnn_reshape_channel_shuffle_nc_x32(
      |                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                     xnn_reshape_transpose_nd_x32
/var/lib/jenkins/workspace/aten/src/ATen/native/xnnpack/ChannelShuffle.cpp:91:35: error: ‘xnn_setup_channel_shuffle_nc_x32’ was not declared in this scope
   91 |   const xnn_status setup_status = xnn_setup_channel_shuffle_nc_x32(
      |        

2025-12-02T16:09:15.4397470Z ##[endgroup]
2025-12-02T16:09:15.9414874Z Traceback (most recent call last):
2025-12-02T16:09:15.9418660Z   File "/usr/lib64/python3.9/runpy.py", line 197, in _run_module_as_main
2025-12-02T16:09:15.9422712Z     return _run_code(code, main_globals, None,
2025-12-02T16:09:15.9427476Z   File "/usr/lib64/python3.9/runpy.py", line 87, in _run_code
2025-12-02T16:09:15.9431620Z     exec(code, run_globals)
2025-12-02T16:09:15.9432735Z   File "/home/ec2-user/actions-runner/_work/pytorch/pytorch/tools/stats/upload_utilization_stats/upload_utilization_stats.py", line 17, in <module>
2025-12-02T16:09:15.9433284Z     from tools.stats.utilization_stats_lib import (
2025-12-02T16:09:15.9433747Z   File "/home/ec2-user/actions-runner/_work/pytorch/pytorch/tools/stats/utilization_stats_lib.py", line 13, in <module>
2025-12-02T16:09:15.9434166Z     class UtilizationStats:
2025-12-02T16:09:15.9434577Z   File "/home/ec2-user/actions-runner/_work/pytorch/pytorch/tools/stats/utilization_stats_lib.py", line 14, in UtilizationStats
2025-12-02T16:09:15.9435013Z     avg: float | None = None
2025-12-02T16:09:15.9435289Z TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'
2025-12-02T16:09:15.9941008Z ##[error]Process completed with exit code 1.

@pytorchbot: error: unrecognized arguments: cuda failure is unrelated

usage: @pytorchbot [-h] {merge,revert,rebase,label,drci,cherry-pick} ...

usage: @pytorchbot [-h] {merge,revert,rebase,label,drci,cherry-pick} ...

In order to invoke the bot on your PR, include a line that starts with
@pytorchbot anywhere in a comment. That line will form the command; no
multi-line commands are allowed. Some commands may be used on issues as specified below.

Example:
    Some extra context, blah blah, wow this PR looks awesome

    @pytorchbot merge

optional arguments:
  -h, --help            Show this help message and exit.

command:
  {merge,revert,rebase,label,drci,cherry-pick}
    merge               Merge a PR
    revert              Revert a PR
    rebase              Rebase a PR
    label               Add label to a PR
    drci                Update Dr. CI
    cherry-pick         Cherry pick a PR onto a release branch

usage: @pytorchbot merge [-f MESSAGE | -i] [-ic] [-r [{viable/strict,main}]]

Merge an accepted PR, subject to the rules in .github/merge_rules.json.
By default, this will wait for all required checks (lint, pull) to succeed before merging.

optional arguments:
  -f MESSAGE, --force MESSAGE
                        Merge without checking anything. This requires a reason for auditting purpose, for example:
                        @pytorchbot merge -f 'Minor update to fix lint. Expecting all PR tests to pass'
                        
                        Please use `-f` as last resort, prefer `--ignore-current` to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.
  -i, --ignore-current  Merge while ignoring the currently failing jobs.  Behaves like -f if there are no pending jobs.
  -ic                   Old flag for --ignore-current. Deprecated in favor of -i.
  -r [{viable/strict,main}], --rebase [{viable/strict,main}]
                        Rebase the PR to re run checks before merging.  Accepts viable/strict or main as branch options and will default to viable/strict if not specified.

usage: @pytorchbot revert -m MESSAGE -c
                          {nosignal,ignoredsignal,landrace,weird,ghfirst,autorevert}

Revert a merged PR. This requires that you are a Meta employee.

Example:
  @pytorchbot revert -m="This is breaking tests on trunk. hud.pytorch.org/" -c=nosignal

optional arguments:
  -m MESSAGE, --message MESSAGE
                        The reason you are reverting, will be put in the commit message. Must be longer than 3 words.
  -c {nosignal,ignoredsignal,landrace,weird,ghfirst,autorevert}, --classification {nosignal,ignoredsignal,landrace,weird,ghfirst,autorevert}
                        A machine-friendly classification of the revert reason.

usage: @pytorchbot rebase [-s | -b BRANCH]

Rebase a PR. Rebasing defaults to the stable viable/strict branch of pytorch.
Repeat contributor may use this command to rebase their PR.

optional arguments:
  -s, --stable          [DEPRECATED] Rebase onto viable/strict
  -b BRANCH, --branch BRANCH
                        Branch you would like to rebase to

usage: @pytorchbot label labels [labels ...]

Adds label to a PR or Issue [Can be used on Issues]

positional arguments:
  labels  Labels to add to given Pull Request or Issue [Can be used on Issues]

usage: @pytorchbot drci 

Update Dr. CI. Updates the Dr. CI comment on the PR in case it's gotten out of sync with actual CI results.

usage: @pytorchbot cherry-pick --onto ONTO [--fixes FIXES] -c
                               {regression,critical,fixnewfeature,docs,release}

Cherry pick a pull request onto a release branch for inclusion in a release

optional arguments:
  --onto ONTO, --into ONTO
                        Branch you would like to cherry pick onto (Example: release/2.1)
  --fixes FIXES         Link to the issue that your PR fixes (Example: https://github.com/pytorch/pytorch/issues/110666)
  -c {regression,critical,fixnewfeature,docs,release}, --classification {regression,critical,fixnewfeature,docs,release}
                        A machine-friendly classification of the cherry-pick reason.