Skip to content

Conversation

@Sebastian-Larsson
Copy link
Collaborator

@Sebastian-Larsson Sebastian-Larsson commented Nov 4, 2025

@Sebastian-Larsson Sebastian-Larsson added the partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm label Nov 4, 2025
@Sebastian-Larsson Sebastian-Larsson added ciflow/trunk release notes: examples Changes to any of our example LLMs integrations, such as Llama3 and Llava module: llm Issues related to LLM examples and apps, and to the extensions/llm/ code labels Nov 4, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Nov 4, 2025

🔗 Helpful Links

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

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

❌ 9 New Failures, 1 Pending, 2 Unrelated Failures

As of commit f4cf8c0 with merge base b17004c (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

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

@meta-cla meta-cla 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 Nov 4, 2025
@zingo
Copy link
Collaborator

zingo commented Nov 11, 2025

Hi @SS-JIA this one is outside of Arm stuff so we need help with someone to review it, thanks for your time and effort with this.

@SS-JIA
Copy link
Contributor

SS-JIA commented Nov 11, 2025

Requested review from @larryliu0820

llm_config.quantization.pt2e_quantize.value
)
quantizers.append(coreml_quantizer)
if llm_config.backend.tosa.enabled and llm_config.quantization.pt2e_quantize:
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it possible to add a unit test to cover this logic branch?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Let me know what you think

@Sebastian-Larsson
Copy link
Collaborator Author

@larryliu0820 woul you mind taking another look with the changes after your comments?

@zingo
Copy link
Collaborator

zingo commented Dec 4, 2025

@metascroy Is this OK to merge?

@zingo
Copy link
Collaborator

zingo commented Dec 15, 2025

Hi @larryliu0820 (and/or @digantdesai ) is this OK after the added test? We have some follow up PR that would be good to get into PR state :)

@SS-JIA
Copy link
Contributor

SS-JIA commented Jan 7, 2026

@larryliu0820 new test case was added - mind taking a look? Thanks in advance!

Copy link
Contributor

@SS-JIA SS-JIA left a comment

Choose a reason for hiding this comment

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

LGTM as the requested test was added!

Copy link
Contributor

@SS-JIA SS-JIA left a comment

Choose a reason for hiding this comment

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

Temporary RC while I double check internal importing the diff

@meta-codesync
Copy link
Contributor

meta-codesync bot commented Jan 14, 2026

@SS-JIA has imported this pull request. If you are a Meta employee, you can view this in D90692071.

@SS-JIA
Copy link
Contributor

SS-JIA commented Jan 14, 2026

Indeed, the new test is failing due to the Arm targets not being visible to the test target.

To fix, update: https://github.com/pytorch/executorch/blob/8293fa64d221c1d694723b9c209fe0eeb34a8748/examples/models/llama/tests/TARGETS

Add the "//executorch/backends/arm/quantizer:lib" target as a dependency

@larryliu0820
Copy link
Contributor

Looks good as long as CI jobs are fixed.

@zingo zingo removed this from the 1.1.0 milestone Jan 28, 2026
@zingo zingo moved this from To triage to In progress in ExecuTorch Arm Backend Jan 28, 2026
@zingo zingo requested a review from SS-JIA January 29, 2026 10:27
@zingo
Copy link
Collaborator

zingo commented Jan 29, 2026

Rebasing as we just merged a tosa spec change just to make sure all is still working :)

@zingo
Copy link
Collaborator

zingo commented Jan 30, 2026

@SS-JIA we fixed the buck2 things and now it needs to be re-imported as we cant merge with the version diff vs meta internal.

@zingo zingo added this to the 1.2.0 milestone Feb 2, 2026
Change-Id: I2cded64d7ffdf3de441bbd7ee73357c8ba0a3749
Signed-off-by: Sebastian Larsson <sebastian.larsson@arm.com>
@Sebastian-Larsson
Copy link
Collaborator Author

Updated from TARGETS to BUCK

@zingo
Copy link
Collaborator

zingo commented Feb 3, 2026

@SS-JIA Can you help reimporting? And maybe review if it's green?

@SS-JIA
Copy link
Contributor

SS-JIA commented Feb 3, 2026

@zingo apologies for the delay. I triggered a re-import but still seeing some failures internally - currently trying to figure out what is needed to get everything green, and will post an update ASAP

SS-JIA pushed a commit to SS-JIA/executorch-1 that referenced this pull request Feb 3, 2026
Summary:
cc freddan80 per zingo oscarandersson8218 digantdesai larryliu0820 mergennachin cccclai helunwencser jackzhxng

Pull Request resolved: pytorch#15556

Differential Revision: D90692071

Pulled By: SS-JIA
@SS-JIA
Copy link
Contributor

SS-JIA commented Feb 3, 2026

@Sebastian-Larsson @zingo I created #17183 to demonstrate the fixes are that needed to get things working in Meta-internal repo!

To minimize the land time, I think we can either:

  • Stamp / land the PR I created - I can take care of any further fixes needed for internal tests to pass
  • Incorporate the changes from the PR I created into this one, I'll re-import and double check tests pass

I do notice some arm related failures on this PR, though - I presume those are unrelated to these changes, and there are no other planned updates to this PR?

@Sebastian-Larsson
Copy link
Collaborator Author

@Sebastian-Larsson @zingo I created #17183 to demonstrate the fixes are that needed to get things working in Meta-internal repo!

To minimize the land time, I think we can either:

* Stamp / land the PR I created - I can take care of any further fixes needed for internal tests to pass

* Incorporate the changes from the PR I created into this one, I'll re-import and double check tests pass

I do notice some arm related failures on this PR, though - I presume those are unrelated to these changes, and there are no other planned updates to this PR?

Landing the PR you created seems like the smoother option if you don't mind!

SS-JIA pushed a commit that referenced this pull request Feb 4, 2026
This diff is to facilitate the landing of #15556

Differential Revision: [D92280949](https://our.internmc.facebook.com/intern/diff/D92280949/)

[ghstack-poisoned]
SS-JIA pushed a commit that referenced this pull request Feb 4, 2026
This diff is to facilitate the landing of #15556

Differential Revision: [D92280949](https://our.internmc.facebook.com/intern/diff/D92280949/)

ghstack-source-id: 338222346
Pull Request resolved: #17205
@SS-JIA
Copy link
Contributor

SS-JIA commented Feb 4, 2026

Of course. I'll take it from here!

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

Labels

ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. module: llm Issues related to LLM examples and apps, and to the extensions/llm/ code partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm release notes: examples Changes to any of our example LLMs integrations, such as Llama3 and Llava

Projects

Status: In progress

Development

Successfully merging this pull request may close these issues.

4 participants