FBGEMM
FBGEMM copied to clipboard
pytorch
Revert D57738223: Multisect successfully blamed "D57738223: [fp8 kv cache] wmma_gqa_attn_splitk" for one test failure
Summary: This diff reverts D57738223 D57738223: [fp8 kv cache] wmma_gqa_attn_splitk by Aya-ZIbra causes the following test failure:
Tests affected:
Here's the Multisect link: https://www.internalfb.com/multisect/5328620 Here are the tasks that are relevant to this breakage: T191387507: 10+ tests failing for gpu_lowering
The backout may land if someone accepts it.
If this diff has been generated in error, you can Commandeer and Abandon it.
Reviewed By: Aya-ZIbra
Differential Revision: D58237911
Deploy Preview for pytorch-fbgemm-docs ready!
| Name | Link |
|---|---|
| Latest commit | 158a7870a4248e3ba6b300e88e73b38db739e611 |
| Latest deploy log | https://app.netlify.com/sites/pytorch-fbgemm-docs/deploys/6661da1e627bc90008e8992e |
| Deploy Preview | https://deploy-preview-2695--pytorch-fbgemm-docs.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @Aya-ZIbra!
Thank you for your pull request.
We require contributors to sign our Contributor License Agreement, and yours needs attention.
You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.
Process
In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.
Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.
If you have received this in error or have any questions, please contact us at [email protected]. Thanks!