Skip to content

Conversation

psiddh
Copy link
Contributor

@psiddh psiddh commented Sep 22, 2025

Summary:
Fix the JNI layer at the time of throwing the exception. Change the return type from 'ExecutorchRuntimeException' to 'RuntimeException'

Also disable readLogBuffer from exception flow , A follow up change will address this. This way it keeps this change to a minimum and unblocks few Teams for now

Differential Revision: D82995994

Summary:
Fix the JNI layer at the time of throwing the exception. Change the return type from 'ExecutorchRuntimeException' to 'RuntimeException'

Also disable readLogBuffer from exception flow , A follow up change will address this. This way it keeps this change to a minimum and unblocks few Teams for now

Differential Revision: D82995994
Copy link

pytorch-bot bot commented Sep 22, 2025

🔗 Helpful Links

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

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

❌ 2 New Failures, 1 Unrelated Failure

As of commit ed0ad47 with merge base c9f46e2 (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following job failed but was 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 Sep 22, 2025
@facebook-github-bot
Copy link
Contributor

@psiddh has exported this pull request. If you are a Meta employee, you can view the originating diff in D82995994.

Copy link

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.

@facebook-github-bot
Copy link
Contributor

@psiddh has imported this pull request. If you are a Meta employee, you can view this in D82995994.

@psiddh psiddh merged commit 00ea1b7 into pytorch:main Sep 23, 2025
128 of 131 checks passed
@psiddh psiddh deleted the export-D82995994 branch September 23, 2025 01:57
@psiddh
Copy link
Contributor Author

psiddh commented Sep 23, 2025

@pytorchbot cherry-pick --onto release/1.0 -c critical

pytorchbot pushed a commit that referenced this pull request Sep 23, 2025
Summary:
Fix the JNI layer at the time of throwing the exception. Change the
return type from 'ExecutorchRuntimeException' to 'RuntimeException'

Also disable readLogBuffer from exception flow , A follow up change will
address this. This way it keeps this change to a minimum and unblocks
few Teams for now

Differential Revision: D82995994

(cherry picked from commit 00ea1b7)
@pytorchbot
Copy link
Collaborator

Cherry picking #14483

The cherry pick PR is at #14498 and it is recommended to link a critical cherry pick PR with an issue. The following tracker issues are updated:

Details for Dev Infra team Raised by workflow job

StrycekSimon pushed a commit to nxp-upstream/executorch that referenced this pull request Sep 23, 2025
…#14483)

Summary:
Fix the JNI layer at the time of throwing the exception. Change the
return type from 'ExecutorchRuntimeException' to 'RuntimeException'

Also disable readLogBuffer from exception flow , A follow up change will
address this. This way it keeps this change to a minimum and unblocks
few Teams for now

Differential Revision: D82995994
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 meta-exported
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants