[1/N] Enable unused variable warnings on torch_cpu and fix some violations

[cyyever]

Fixes #ISSUE_NUMBER

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @EikanWang

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/128670

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• NVIDIA runners have a blacklog of 2000+ jobs

❌ 1 New Failure, 1 Cancelled Job, 17 Unrelated Failures

As of commit 5e11812 with merge base eb1583d ():

NEW FAILURE - The following job has failed:

• linux-binary-manywheel / manywheel-py3_8-cuda11_8-split-test / test (gh)
  Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under '/home/ec2-user/actions-runner/_work/pytorch/pytorch/pytorch/.github/actions/chown-workspace'. Did you forget to run actions/checkout before running your local action?

CANCELLED JOB - The following job was cancelled. Please retry:

• periodic / linux-focal-cuda12.4-py3.10-gcc9 / test (default, 5, 5, linux.4xlarge.nvidia.gpu) (gh)
  ##[error]The operation was canceled.

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

• linux-binary-conda / conda-py3_8-cuda11_8-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-conda / conda-py3_9-cuda12_4-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-libtorch-cxx11-abi / libtorch-cuda11_8-shared-with-deps-cxx11-abi-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-libtorch-cxx11-abi / libtorch-cuda12_1-shared-with-deps-cxx11-abi-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-libtorch-pre-cxx11 / libtorch-cuda12_4-shared-with-deps-pre-cxx11-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-manywheel / manywheel-py3_10-cuda12_1-upload / upload (gh) (matched linux rule in flaky-rules.json)
  Error response from daemon: Head "https://registry-1.docker.io/v2/continuumio/miniconda3/manifests/4.12.0": Get "https://auth.docker.io/token?account=githubactions&scope=repository%3Acontinuumio%2Fminiconda3%3Apull&service=registry.docker.io": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
• linux-binary-manywheel / manywheel-py3_11-cuda12_1-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-manywheel / manywheel-py3_11-cuda12_4-split-upload / upload (gh) (matched linux rule in flaky-rules.json)
  Error response from daemon: Head "https://registry-1.docker.io/v2/continuumio/miniconda3/manifests/4.12.0": Get "https://auth.docker.io/token?account=githubactions&scope=repository%3Acontinuumio%2Fminiconda3%3Apull&service=registry.docker.io": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
• linux-binary-manywheel / manywheel-py3_11-cuda12_4-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-manywheel / manywheel-py3_12-cuda11_8-split-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-manywheel / manywheel-py3_12-cuda12_1-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-manywheel / manywheel-py3_12-cuda12_4-split-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-manywheel / manywheel-py3_8-cuda12_1-split-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-manywheel / manywheel-py3_8-cuda12_1-upload / upload (gh) (matched linux rule in flaky-rules.json)
  Error response from daemon: Head "https://registry-1.docker.io/v2/continuumio/miniconda3/manifests/4.12.0": Get "https://auth.docker.io/token?account=githubactions&scope=repository%3Acontinuumio%2Fminiconda3%3Apull&service=registry.docker.io": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
• linux-binary-manywheel / manywheel-py3_8-cuda12_4-split-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128
• linux-binary-manywheel / manywheel-py3_9-cuda12_1-test / test (gh) (matched linux rule in flaky-rules.json)
  The process '/usr/bin/git' failed with exit code 128

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• periodic / win-vs2019-cuda11.8-py3 / test (default, 3, 4, windows.g5.4xlarge.nvidia.gpu) (gh) (trunk failure)
  profiler\test_cpp_thread.py::CppThreadTest::test_profile_memory

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[cyyever]

@pytorchbot rebase -b main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

Successfully rebased torch_cpu_warning onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout torch_cpu_warning && git pull --rebase)

[cyyever]

@pytorchbot rebase -b main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

Successfully rebased torch_cpu_warning onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout torch_cpu_warning && git pull --rebase)

[cyyever]

@pytorchbot rebase -b main

[pytorchmergebot]

@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here

[pytorchmergebot]

Successfully rebased torch_cpu_warning onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout torch_cpu_warning && git pull --rebase)

[cyyever]

@pytorchmergebot merge -f "Failures are unrelated"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here