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

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 9, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure, 2 Cancelled Jobs, 29 Pending

As of commit 7b2b3aa with merge base 2eb8994 (image):

NEW FAILURE - The following job has failed:

CANCELLED JOBS - The following jobs were cancelled. Please retry:

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 Oct 9, 2025
@github-actions
Copy link

github-actions bot commented Oct 9, 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.

@lucylq lucylq force-pushed the gh/lucylq/119/orig branch from 85033ca to 21a323b Compare October 9, 2025 21:52
Pull Request resolved: #14767


ghstack-source-id: 315148398

Differential Revision: [D83799869](https://our.internmc.facebook.com/intern/diff/D83799869/)
@lucylq lucylq force-pushed the gh/lucylq/119/orig branch from 21a323b to 7b2b3aa Compare October 9, 2025 22:06
@lucylq lucylq merged commit d0827e5 into main Oct 9, 2025
137 of 140 checks passed
@lucylq lucylq deleted the gh/lucylq/119/orig branch October 9, 2025 22:33
@lucylq
Copy link
Contributor

lucylq commented Oct 9, 2025

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

@pytorchbot
Copy link
Collaborator Author

Cherry picking #14966

Command git -C /home/runner/work/executorch/executorch cherry-pick -x -X theirs d0827e51bc685312527387eac796cceca49e2e61 returned non-zero exit code 1

Auto-merging extension/module/CMakeLists.txt
Auto-merging extension/module/test/targets.bzl
CONFLICT (modify/delete): extension/named_data_map/merged_data_map.cpp deleted in HEAD and modified in d0827e51bc (Use merged data map in module (#14966)).  Version d0827e51bc (Use merged data map in module (#14966)) of extension/named_data_map/merged_data_map.cpp left in tree.
CONFLICT (modify/delete): extension/named_data_map/merged_data_map.h deleted in HEAD and modified in d0827e51bc (Use merged data map in module (#14966)).  Version d0827e51bc (Use merged data map in module (#14966)) of extension/named_data_map/merged_data_map.h left in tree.
CONFLICT (modify/delete): extension/named_data_map/test/merged_data_map_test.cpp deleted in HEAD and modified in d0827e51bc (Use merged data map in module (#14966)).  Version d0827e51bc (Use merged data map in module (#14966)) of extension/named_data_map/test/merged_data_map_test.cpp left in tree.
error: could not apply d0827e51bc... Use merged data map in module (#14966)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Details for Dev Infra team Raised by workflow job

@lucylq
Copy link
Contributor

lucylq commented Oct 10, 2025

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

@pytorchbot
Copy link
Collaborator Author

Cherry picking #14966

Command git -C /home/runner/work/executorch/executorch cherry-pick -x -X theirs d0827e51bc685312527387eac796cceca49e2e61 returned non-zero exit code 1

Auto-merging extension/module/CMakeLists.txt
Auto-merging extension/module/test/targets.bzl
CONFLICT (modify/delete): extension/named_data_map/merged_data_map.cpp deleted in HEAD and modified in d0827e51bc (Use merged data map in module (#14966)).  Version d0827e51bc (Use merged data map in module (#14966)) of extension/named_data_map/merged_data_map.cpp left in tree.
CONFLICT (modify/delete): extension/named_data_map/merged_data_map.h deleted in HEAD and modified in d0827e51bc (Use merged data map in module (#14966)).  Version d0827e51bc (Use merged data map in module (#14966)) of extension/named_data_map/merged_data_map.h left in tree.
CONFLICT (modify/delete): extension/named_data_map/test/merged_data_map_test.cpp deleted in HEAD and modified in d0827e51bc (Use merged data map in module (#14966)).  Version d0827e51bc (Use merged data map in module (#14966)) of extension/named_data_map/test/merged_data_map_test.cpp left in tree.
error: could not apply d0827e51bc... Use merged data map in module (#14966)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Details for Dev Infra team Raised by workflow job

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.

2 participants