Skip to content

try to fix regression#176756

Closed
laithsakka wants to merge 1 commit intogh/laithsakka/420/basefrom
gh/laithsakka/420/head
Closed

try to fix regression#176756
laithsakka wants to merge 1 commit intogh/laithsakka/420/basefrom
gh/laithsakka/420/head

Conversation

@laithsakka
Copy link
Contributor

@laithsakka laithsakka commented Mar 6, 2026

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Mar 6, 2026

🔗 Helpful Links

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

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

⏳ 11 Pending, 1 Unrelated Failure

As of commit 5b9da73 with merge base dc49385 (image):

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:

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

laithsakka added a commit that referenced this pull request Mar 6, 2026
ghstack-source-id: a0cadc6
Pull Request resolved: #176756
@pytorch-bot
Copy link

pytorch-bot bot commented Mar 6, 2026

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.

@laithsakka laithsakka marked this pull request as draft March 6, 2026 23:20
@laithsakka laithsakka closed this Mar 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant