Skip to content

Conversation

@metascroy
Copy link
Contributor

Summary: This diff adds extra logging in CoreML to indicate whether the model in the pte file was pre-compiled.

Differential Revision: D81256207

Summary: This diff adds extra logging in CoreML to indicate whether the model in the pte file was pre-compiled.

Differential Revision: D81256207
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 2, 2025

🔗 Helpful Links

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

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 1 New Failure, 1 Cancelled Job, 2 Unrelated Failures

As of commit cad826f with merge base 6c1ef96 (image):

NEW FAILURE - The following job has failed:

CANCELLED JOB - The following job was cancelled. Please retry:

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

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

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 Sep 2, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D81256207

@github-actions
Copy link

github-actions bot commented Sep 2, 2025

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@metascroy
Copy link
Contributor Author

@cymbalrush can you take a look at this PR to add extra logging to the CoreML delegate?

@cymbalrush
Copy link
Contributor

Looks good, thank you!

@metascroy metascroy merged commit 0b4de82 into pytorch:main Sep 3, 2025
120 of 133 checks passed
metascroy added a commit to metascroy/executorch that referenced this pull request Sep 16, 2025
Summary:
Original commit changeset: ae667b071853

Original Phabricator Diff: D81256207

Since the introduction of D80715432, WhatsApp is seeing an increase in model load failures with error code 0x23 (P1948468840).  From logs, the underlying issue is something like "Model init failed “model.mlmodelc” couldn’t be moved to “models” because an item with the same name already exists."

FB app has also seen an increase in error code 0x23 since 9/5.

We are unable to reproduce this error locally, but out of caution we want to revert D80715432 and see if the errors resolve.

Since D80715432 landed, we also landed D81256207 to add more logging.  To prevent conflicts, we backout in 3 steps:

* In diff 1/3, we backout D81256207, which added more logging
* In diff 2/3, we backout D80715432, which is the problematic diff we're trying to revert
* In diff 3/3, we introduce some of the logging we backed out in diff 1/3

Differential Revision: D82581442
metascroy added a commit to metascroy/executorch that referenced this pull request Sep 16, 2025
Summary:

Original commit changeset: ae667b071853

Original Phabricator Diff: D81256207

Since the introduction of D80715432, WhatsApp is seeing an increase in model load failures with error code 0x23 (P1948468840).  From logs, the underlying issue is something like "Model init failed “model.mlmodelc” couldn’t be moved to “models” because an item with the same name already exists."

FB app has also seen an increase in error code 0x23 since 9/5.

We are unable to reproduce this error locally, but out of caution we want to revert D80715432 and see if the errors resolve.

Since D80715432 landed, we also landed D81256207 to add more logging.  To prevent conflicts, we backout in 3 steps:

* In diff 1/3, we backout D81256207, which added more logging
* In diff 2/3, we backout D80715432, which is the problematic diff we're trying to revert
* In diff 3/3, we introduce some of the logging we backed out in diff 1/3

Differential Revision: D82581442
metascroy added a commit to metascroy/executorch that referenced this pull request Sep 16, 2025
Summary:

Original commit changeset: ae667b071853

Original Phabricator Diff: D81256207

Since the introduction of D80715432, WhatsApp is seeing an increase in model load failures with error code 0x23 (P1948468840).  From logs, the underlying issue is something like "Model init failed “model.mlmodelc” couldn’t be moved to “models” because an item with the same name already exists."

FB app has also seen an increase in error code 0x23 since 9/5.

We are unable to reproduce this error locally, but out of caution we want to revert D80715432 and see if the errors resolve.

Since D80715432 landed, we also landed D81256207 to add more logging.  To prevent conflicts, we backout in 3 steps:

* In diff 1/3, we backout D81256207, which added more logging
* In diff 2/3, we backout D80715432, which is the problematic diff we're trying to revert
* In diff 3/3, we introduce some of the logging we backed out in diff 1/3

Differential Revision: D82581442
facebook-github-bot pushed a commit that referenced this pull request Sep 17, 2025
Differential Revision: D82581442

Pull Request resolved: #14353
StrycekSimon pushed a commit to nxp-upstream/executorch that referenced this pull request Sep 23, 2025
Differential Revision: D82581442

Pull Request resolved: pytorch#14353
pytorchbot pushed a commit that referenced this pull request Sep 25, 2025
Differential Revision: D82581442

Pull Request resolved: #14353

(cherry picked from commit 75cb986)
GregoryComer pushed a commit that referenced this pull request Sep 26, 2025
Summary:
Original commit changeset: ae667b071853

Original Phabricator Diff: D81256207

* In diff 1/3, we backout D81256207, which added more logging
* In diff 2/3, we backout D80715432, which is the problematic diff we're
trying to revert
* In diff 3/3, we introduce some of the logging we backed out in diff
1/3

Differential Revision: D82581442

Co-authored-by: Scott Roy <[email protected]>
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. fb-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants