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: #14479 by @mergennachin
^ 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/mergennachin/1/base
ghstack PR head: https://github.com/pytorch/executorch/tree/gh/mergennachin/1/head
Merge bot PR base: https://github.com/pytorch/executorch/tree/main
Merge bot PR head: https://github.com/pytorch/executorch/tree/gh/mergennachin/1/orig
Differential Revision: D82991084
@diff-train-skip-merge

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

ghstack-source-id: 311318478
Pull Request resolved: #14479
@pytorch-bot
Copy link

pytorch-bot bot commented Sep 22, 2025

🔗 Helpful Links

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

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

❌ 2 New Failures, 18 Pending, 1 Unrelated Failure

As of commit 2cb0731 with merge base 685e795 (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
@github-actions
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.

mergennachin added a commit that referenced this pull request Sep 22, 2025
Test Plan: 

Ran

```
python .github/scripts/propose_ghstack_orig_pr.py --repo pytorch/executorch --ref 14368
``` 

and print out `bot_metadata` variable.  Here's the output: 

https://gist.github.com/mergennachin/8a5b44fded2f584fe7453ecd4e24b69c

Also tested via ghexport via internal phabricator. It eventually
produced this PR: #14481
StrycekSimon pushed a commit to nxp-upstream/executorch that referenced this pull request Sep 23, 2025
Test Plan: 

Ran

```
python .github/scripts/propose_ghstack_orig_pr.py --repo pytorch/executorch --ref 14368
``` 

and print out `bot_metadata` variable.  Here's the output: 

https://gist.github.com/mergennachin/8a5b44fded2f584fe7453ecd4e24b69c

Also tested via ghexport via internal phabricator. It eventually
produced this PR: pytorch#14481
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.

3 participants