Skip to content

Conversation

@pytorchbot
Copy link
Collaborator

This PR was created by the merge bot to help merge the original PR into the main branch.
ghstack PR number: #7745
^ Please use this as the source of truth for the PR details, comments, and reviews
ghstack PR base: https://github.com/pytorch/executorch/tree/gh/digantdesai/3/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/digantdesai/3/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/gh/digantdesai/2/orig
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/digantdesai/3/orig
@diff-train-skip-merge

@pytorch-bot
Copy link

pytorch-bot bot commented Jan 22, 2025

🔗 Helpful Links

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

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

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jan 22, 2025
Base automatically changed from gh/digantdesai/2/orig to main January 22, 2025 19:53
Pull Request resolved: #7745

* Added a few qd8 fp16 tests for qc4w and qc8w
* Cleaned up and split fp16 and fp32 for basic tests to avoid getting confused regarding atol issues
* Created a TODO to look into atol values
ghstack-source-id: 262438488
@exported-using-ghexport

Differential Revision: [D68350952](https://our.internmc.facebook.com/intern/diff/D68350952/)
@kirklandsign kirklandsign force-pushed the gh/digantdesai/3/orig branch from 7a3ff2f to 56f92ee Compare January 22, 2025 19:54
@kirklandsign kirklandsign merged commit 2db2bd2 into main Jan 22, 2025
30 of 33 checks passed
@kirklandsign kirklandsign deleted the gh/digantdesai/3/orig branch January 22, 2025 19:54
@github-actions
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants