Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[spmd_types] no_typecheck FlexAttention#186190

Draft
pianpwk wants to merge 1 commit into
gh/pianpwk/144/basefrom
gh/pianpwk/144/head
Draft

[spmd_types] no_typecheck FlexAttention#186190
pianpwk wants to merge 1 commit into
gh/pianpwk/144/basefrom
gh/pianpwk/144/head

Conversation

@pianpwk
Copy link
Copy Markdown
Contributor

@pianpwk pianpwk commented Jun 4, 2026 •
edited
Loading

@pianpwk
Update
e19120d 
[ghstack-poisoned]
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Jun 4, 2026 •
edited
Loading

🔗 Helpful Links

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

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

❌ 2 New Failures, 1 Unrelated Failure, 1 Unclassified Failure

As of commit e19120d with merge base ca1d5ef (image):

NEW FAILURES - The following jobs have failed:

UNCLASSIFIED FAILURE - DrCI could not classify the following job because the workflow did not run on the merge base. The failure may be pre-existing on trunk or introduced by this PR:

  • Check mergeability of ghstack PR / ghstack-mergeability-check (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)
    RuntimeError: PR 181519 is out of sync with the corresponding revision 64bea984df72c30da204ccc45d26d9458dd5dac8 on branch gh/pianpwk/138/orig that would be merged into main. This usually happens because there is a non ghstack change in the PR. Please sync them and try again (ex. make the changes on origin/gh/pianpwk/144/orig and run ghstack).

BROKEN TRUNK - The following job failed but were 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.

@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Jun 4, 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.

This was referenced Jun 4, 2026
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@drisspg drisspg Awaiting requested review from drisspg drisspg will be requested when the pull request is marked ready for review drisspg is a code owner

Assignees

No one assigned

Labels

ciflow/inductor ciflow/torchtitan Run TorchTitan integration tests module: inductor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@pianpwk