[BE] Enable ruff's UP rules in pyproject.toml

[justinchuby]

Stack from ghstack (oldest at bottom):

• [BE] f-stringify torch/ and scripts #105538
• -> [BE] Enable ruff's UP rules in pyproject.toml #105437

Signed-off-by: Justin Chu justinchu@microsoft.com

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @ngimel @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov

[pytorch-bot]

🔗 Helpful Links

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

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

✅ 4 Unrelated Failures

As of commit d8932d0:

UNSTABLE - The following jobs failed but were likely due to flakiness present on trunk and has been marked as unstable:

• cuda11.8-py3.10-gcc7-sm86 / test (inductor_torchbench, 1, 1, linux.g5.4xlarge.nvidia.gpu, unstable) (gh)
• linux-bionic-cuda11.8-py3.10-gcc9 / test (distributed, 3, 3, linux.8xlarge.nvidia.gpu, unstable) (gh)
• linux-focal-py3.8-gcc7 / test (distributed, 1, 2, linux.2xlarge, unstable) (gh)
• linux-focal-rocm5.6-py3.8 / test (default, 2, 3, linux.rocm.gpu, unstable) (gh)

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

[huydhn]

In the future, please consider breaking up this stack into multiple smaller ones of may be 2 to 3 depth each because this would very likely increase queue time on CI for scarce resources like ROCm, MacOS, or Windows. A stack of depth 15 means 15 times the regular number of CI jobs at once. As this has already started and the changes are lint-related, I would probably wait and cross my fingers that they all pass :)

cc @seemethere @malfet

[justinchuby]

In the future, please consider breaking up this stack into multiple smaller ones of may be 2 to 3 depth each because this would very likely increase queue time on CI for scarce resources like ROCm, MacOS, or Windows. A stack of depth 15 means 15 times the regular number of CI jobs at once. As this has already started and the changes are lint-related, I would probably wait and cross my fingers that they all pass :)

Sounds very reasonable. Thanks!

[justinchuby]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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 mandatory check(s) failed. The first few are:

• Lint / lintrunner / linux-job

Dig deeper by viewing the failures on hud

Details for Dev Infra team

Raised by workflow job

Failing merge rule: Core Maintainers

[justinchuby]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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