🔗 Helpful Links

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

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

As of commit f608d1a with merge base 51b6126 ():

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

@pytorchbot rebase -b main

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

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

@pytorchot merge -f "This sounds OK to me"

Hmm, can you please elaborate why this only surfaces for XPU builds, but not for the regular torch ones? Instead of pinning distutils, can't we get rid of deprecated path and remove the constraint?

Hi @malfet, thanks for your review and comments. I'm also not sure why just xpu windows build met this issue, because I didn't find where those required packages installed into the Windows runner env. The only thing I can check is that the setuptools version is 72.1.0 for cpu windows build used runner, but the xpu used runner is 75.1.0. And I also agree with your suggestion to remove the deprecated path and move forward, I think we can have another PR to do it. And this PR change is safe enough and necessary to make sure such issue won't appear in the future. I suggest to land this PR firstly to unblock XPU CI test for other PRs. How do you think?

@pytorchbot rebase

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

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

@pytorchbot rebase

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

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

Due to the original issue #141319 has been fixed by #141363, I have updated the PR title and description. @malfet @huydhn do you think whether this is a reasonable change?

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.