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.

Sign up for GitHub

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

Jump to bottom

Run critical models & recipes on pull request #8348

Open
guangy10 opened this issue Feb 10, 2025 · 0 comments
Open

Run critical models & recipes on pull request #8348

guangy10 opened this issue Feb 10, 2025 · 0 comments
Assignees
@guangy10
Labels
enhancement Not as big of a feature, but technically not a bug. Should be easy to fix module: benchmark Issues related to the benchmark infrastructure module: user experience Issues related to reducing friction for users triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Comments

@guangy10
Copy link
Contributor

guangy10 commented Feb 10, 2025 •
edited by pytorch-bot bot
Loading

🚀 The feature, motivation and pitch

To avoid issue like #8154, I think we should run critical models & recipes on pull request if the touched files will affect the model.

Proposed models & recipes:

  • Llama3.2-1B SpinQuant
  • Llama3.2-1B QLora
  • Llama3.2-1B BF16
  • Llama3.2-1B ANE

cc: @kimishpatel @metascroy

Alternatives

No response

Additional context

No response

RFC (Optional)

No response

cc @huydhn @kirklandsign @shoumikhin @mergennachin @byjlw
@guangy10 guangy10 added enhancement Not as big of a feature, but technically not a bug. Should be easy to fix module: benchmark Issues related to the benchmark infrastructure module: user experience Issues related to reducing friction for users triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module labels Feb 10, 2025
@github-project-automation github-project-automation bot moved this to To triage in ExecuTorch DevX Feb 10, 2025
@guangy10 guangy10 self-assigned this Feb 10, 2025
@guangy10 guangy10 moved this to Ready in ExecuTorch Benchmark Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@guangy10 guangy10

Labels
enhancement Not as big of a feature, but technically not a bug. Should be easy to fix module: benchmark Issues related to the benchmark infrastructure module: user experience Issues related to reducing friction for users triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
ExecuTorch Benchmark
Status: Ready
ExecuTorch DevX
Status: To triage
Milestone
No milestone
Development

No branches or pull requests
1 participant
@guangy10