🔗 Helpful Links

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

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit dbc9817 with merge base 11a86ad ():

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

@pytorchbot label "topic: not user facing"

@pytorchbot merge

This PR needs to be approved by an authorized maintainer before merge.

@pytorchbot merge

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

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@jansel On the run that failed, from what I can gather, it seems like it's a compile time instruction count error where the test didn't necessarily fail, but the basic_modules_ListOfLinears_inductor – instruction count dropped by 4.4 % (a “win” but still outside the ±1.5 % band) and the mm_loop_inductor_dynamic_gpu – count rose by 1.52 % (just barely beyond the 1.5 % band). Do you think a re-run of that specific test would fix this or do you think something will have to be changed in the code?

@pytorchbot merge

The job is marked unstable, I think we need to update the expected values.

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

#158177