Remove pinning to ET commit for Zephyr CI job #13388
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13388
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit a0321f1 with merge base 6e520e2 ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
meta-cla
bot
added
the
CLA Signed
BujSet
added
ciflow/trunk
module: arm
Contributor
Author
|
@pytorchbot label "release notes: none" |
pytorch-bot
bot
added
the
release notes: none
BujSet
changed the title
BujSet
force-pushed
the
zephyr_ci_install_executorch_without_pinned_pt_commit
branch
from
9ff3072 to
16ef0f2
Compare
BujSet
force-pushed
the
zephyr_ci_install_executorch_without_pinned_pt_commit
branch
from
9a97123 to
302c89f
Compare
psiddh
approved these changes
Aug 19, 2025
psiddh
changed the title
Contributor
|
FYI, it doesn't run zephyr jobs without ciflow/trunk label. |
agrima1304
pushed a commit
to agrima1304/executorch
that referenced
this pull request
Aug 26, 2025
### Summary Currently, the CI jobs responsible for running the Zephyr tests checkout a past version of ExecuTorch, but runs install_executorch.sh with the pinned pytorch commit. Ideally, we would resolve this with resolving the cmake errors that arise from using the most up-to-date version of executorch, but for now, we can just keep the ExecuTorch and PyTorch checkouts consistent for CI. This should prevent the Zephyr CI tests from failing spuriously on unrelated PRs. ### Test plan [PLEASE REMOVE] How did you test this PR? Please write down any manual commands you used and note down tests that you have written if applicable. --------- Co-authored-by: Siddartha Pothapragada <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Currently, the CI jobs responsible for running the Zephyr tests checkout a past version of ExecuTorch, but runs install_executorch.sh with the pinned pytorch commit. Ideally, we would resolve this with resolving the cmake errors that arise from using the most up-to-date version of executorch, but for now, we can just keep the ExecuTorch and PyTorch checkouts consistent for CI. This should prevent the Zephyr CI tests from failing spuriously on unrelated PRs.
Test plan
[PLEASE REMOVE] How did you test this PR? Please write down any manual commands you used and note down tests that you have written if applicable.