Skip to content

Conversation

@pearu
Copy link
Collaborator

@pearu pearu commented Oct 2, 2025

Stack from ghstack (oldest at bottom):

  • (to be filled)

Pull-Request-resolved: #164354

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

ghstack-source-id: 57a2f7e
Pull-Request-resolved: #164354

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 2, 2025

🔗 Helpful Links

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

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

❌ 2 New Failures, 22 Cancelled Jobs, 1 Pending

As of commit 04a2524 with merge base b5c4f46 (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

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

@pytorch-bot pytorch-bot bot added the module: cpu CPU specific problem (e.g., perf, algorithm) label Oct 2, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2025

This PR needs a release notes: label

If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@pearu pearu closed this Oct 2, 2025
@github-actions github-actions bot deleted the gh/pearu/130/head branch November 2, 2025 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

module: cpu CPU specific problem (e.g., perf, algorithm)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants