Skip to content

Separate ESP32 CI runs by commit - #24472

Open
rascani wants to merge 1 commit into
pytorch:mainfrom
rascani:codex/esp32-ci-concurrency
Open

rascani wants to merge 1 commit into
pytorch:mainfrom
rascani:codex/esp32-ci-concurrency

Conversation

@rascani

@rascani rascani commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Every push to main currently puts the ESP32 workflow in the same concurrency group, so a new commit cancels the previous commit's jobs. In this job, the smoke test and all 16 optimized model cases passed, but the job was marked cancelled when another push arrived.

Use the concurrency group already shared by the other backend test workflows. Including the commit SHA for branch runs lets different main commits finish independently. The group also separates scheduled and manually triggered runs.

Authored with AI assistance using OpenAI Codex.

Test plan

git diff --check passed. Compared the complete concurrency block with all ten test-backend-*.yml workflows and verified that it matches each exactly. No emulator tests were rerun for this workflow scheduling change.

@pytorch-bot

pytorch-bot Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

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

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

✅ You can merge normally! (1 Unrelated Failure)

As of commit a4d9570 with merge base 893d815 (image):

BROKEN TRUNK - The following job 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 Nov 2, 2026
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown

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.

@rascani
rascani marked this pull request as ready for review November 2, 2026 23:08

This branch has not been deployed

No deployments
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