[12/N] Apply ruff UP035 rule

[cyyever]

This PR continues to apply ruff UP035 rule to test code and some remaining torch files.
cc @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @pragupta @msaroufim @dcci @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @chenyang78 @kadeng @muchulee8 @amjames @chauhang @aakhundov @coconutruben @Lucaskabela

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

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

⏳ 46 Pending, 1 Unrelated Failure

As of commit fe9de10 with merge base 4271ffe ():

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

• ⏳ rocm / linux-jammy-rocm-py3.10 / test (default, 1, 6, linux.rocm.gpu.2, unstable) (gh) (#156098)
• ⏳ rocm / linux-jammy-rocm-py3.10 / test (default, 2, 6, linux.rocm.gpu.2, unstable) (gh) (#156098)
• ⏳ rocm / linux-jammy-rocm-py3.10 / test (default, 3, 6, linux.rocm.gpu.2, unstable) (gh) (#156098)
• ⏳ rocm / linux-jammy-rocm-py3.10 / test (default, 4, 6, linux.rocm.gpu.2, unstable) (gh) (#156098)
• ⏳ rocm / linux-jammy-rocm-py3.10 / test (default, 5, 6, linux.rocm.gpu.2, unstable) (gh) (#156098)
• ⏳ rocm / linux-jammy-rocm-py3.10 / test (default, 6, 6, linux.rocm.gpu.2, unstable) (gh) (#156098)
• trunk / linux-jammy-py3-clang12-executorch / test (executorch, 1, 1, lf.linux.2xlarge, unstable) (gh) (#166072)
  examples/models/llama/tests/test_export_llama_lib.py::ExportLlamaLibTest::test_has_expected_ops_and_op_counts

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

[Lucaskabela]

Thanks for the improvements to typing; LGTM

[cyyever]

@pytorchbot merge -i

[pytorchmergebot]

Merge started

Your change will be merged while ignoring the following 0 checks:

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

[pytorchmergebot]

Merge failed

Reason: 1 jobs have failed, first few of them are: Limited CI on H100 / linux-jammy-cuda12_8-py3_10-gcc11-sm90-FA3-ABI-stable-test / test

Details for Dev Infra team

Raised by workflow job

[cyyever]

@pytorchmergebot merge -f "Unrelated failures"

[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

[donigian]

@pytorchbot revert -c ghfirst -m "Temporarily need to revert this to continue a revert for #165076. @cyyever Please re-merge after revert of #165076".

[pytorchmergebot]

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

[pytorchmergebot]

@cyyever your PR has been successfully reverted.

[donigian]

@pytorchbot merge -f "Was reverted to unblock diff train can be safely merged again"

[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