Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Strided Input test for flex attention #128915

Closed
wants to merge 8 commits into from

Conversation

joydddd
Copy link
Contributor

@joydddd joydddd commented Jun 18, 2024

Copy link

pytorch-bot bot commented Jun 18, 2024

🔗 Helpful Links

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

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

✅ You can merge normally! (6 Unrelated Failures)

As of commit 72c63ff with merge base b24787b (image):

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

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

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

UNSTABLE - The following job failed but was likely due to flakiness present on trunk and has been marked as unstable:

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

@joydddd
Copy link
Contributor Author

joydddd commented Jun 19, 2024

Fix flex attention forward for strided inputs.

@@ -194,10 +194,12 @@ def build_subgraph_buffer(
MATMUL_PRECISION = Q.dtype.element_ty

start_m = tl.program_id(0)
off_hz = tl.program_id(1)
off_z = tl.program_id(1) // H
off_h = tl.program_id(1) % H
Copy link
Contributor

Choose a reason for hiding this comment

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

great catch though!

@joydddd joydddd marked this pull request as ready for review June 21, 2024 02:25
test/inductor/test_flex_attention.py Outdated Show resolved Hide resolved
@joydddd
Copy link
Contributor Author

joydddd commented Jun 24, 2024

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Jun 24, 2024
@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

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 mandatory check(s) failed. The first few are:

Dig deeper by viewing the failures on hud

Details for Dev Infra team Raised by workflow job

Failing merge rule: Core Maintainers

@joydddd
Copy link
Contributor Author

joydddd commented Jun 24, 2024

@pytorchbot merge -f 'Unrelated failures'

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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

@huydhn
Copy link
Contributor

huydhn commented Jun 25, 2024

@pytorchbot revert -m 'Sorry for reverting your change but its tests are failing in trunk, i.e. https://hud.pytorch.org/pytorch/pytorch/commit/41bb81b58279f492e72bd270b3b071dd2953ed8c#26627138290' -c weird

I think this is a land race because your base commit is too old (20 days). It would also explain why there are many unrelated failures in the PR

@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
Copy link
Collaborator

@joydddd your PR has been successfully reverted.

pytorchmergebot added a commit that referenced this pull request Jun 25, 2024
@joydddd
Copy link
Contributor Author

joydddd commented Jun 25, 2024

@pytorchmergebot merge

@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

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: trunk / macos-py3-arm64 / test (default, 2, 3, macos-m1-stable)

Details for Dev Infra team Raised by workflow job

@joydddd
Copy link
Contributor Author

joydddd commented Jun 25, 2024

@pytorchmergebot merge -f "Unrelated failure"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

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

@joydddd joydddd removed the Reverted label Jun 26, 2024
@joydddd joydddd deleted the strided_input_test branch June 26, 2024 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants