Skip to content

Conversation

@laithsakka
Copy link
Contributor

@laithsakka laithsakka commented Oct 29, 2025

Stack from ghstack (oldest at bottom):

Address #165081

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 29, 2025

🔗 Helpful Links

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

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

✅ You can merge normally! (2 Unrelated Failures)

As of commit 896fa02 with merge base 32fe4f6 (image):

FLAKY - The following job failed but was likely due to flakiness present on trunk:

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

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

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

laithsakka added a commit that referenced this pull request Oct 29, 2025
ghstack-source-id: 7512250
Pull Request resolved: #166541
laithsakka added a commit that referenced this pull request Oct 29, 2025
ghstack-source-id: 5736602
Pull Request resolved: #166541
laithsakka added a commit that referenced this pull request Oct 29, 2025
ghstack-source-id: ca7c351
Pull Request resolved: #166541
@laithsakka laithsakka requested a review from aditvenk October 29, 2025 20:03
Copy link
Contributor

@mlazos mlazos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, one question when you guard_or_false are we just optimizing the case when it equals 1? I'm guessing we can do something when the value is 1, and recompile if it's not 1 later. But in the other direction we'll just use the unpsecialized code for all cases.

laithsakka added a commit that referenced this pull request Oct 29, 2025
ghstack-source-id: 09a94bc
Pull Request resolved: #166541
@laithsakka
Copy link
Contributor Author

lgtm, one question when you guard_or_false are we just optimizing the case when it equals 1? I'm guessing we can do something when the value is 1, and recompile if it's not 1 later. But in the other direction we'll just use the unpsecialized code for all cases.

yeh when we know one of them is for sure 1 we take the opt path , not that we already know they are not both 1s.
now in the case that we do not know we take the general path and that would be our unbacked semantics for this.

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 30, 2025
@laithsakka laithsakka added topic: not user facing topic category and removed ciflow/trunk Trigger trunk jobs on your pull request labels Oct 30, 2025
@laithsakka
Copy link
Contributor Author

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Oct 30, 2025
@pytorchmergebot
Copy link
Collaborator

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

@atalman
Copy link
Contributor

atalman commented Oct 30, 2025

@pytorchmergebot revert -c ghfirst -m "breaks internal test"

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

pytorchmergebot added a commit that referenced this pull request Oct 30, 2025
This reverts commit 9051940.

Reverted #166541 on behalf of https://github.com/atalman due to breaks internal test ([comment](#166541 (comment)))
@pytorchmergebot
Copy link
Collaborator

@laithsakka your PR has been successfully reverted.

@pytorchmergebot pytorchmergebot added Reverted ci-no-td Do not run TD on this PR labels Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-td Do not run TD on this PR ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request Merged Reverted topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants