Skip to content

Add Cadence CI test workflow with separate build and test signals#18677

Open
aliafzal wants to merge 1 commit intomainfrom
cadence-ci-tests
Open

Add Cadence CI test workflow with separate build and test signals#18677
aliafzal wants to merge 1 commit intomainfrom
cadence-ci-tests

Conversation

@aliafzal
Copy link
Copy Markdown
Contributor

@aliafzal aliafzal commented Apr 2, 2026

Splits Cadence CI into separate build and test jobs with artifact exchange. Build job compiles cadence_runner and uploads it. Test workflow has two parallel jobs: test-aot (Python AOT tests) and test-ops (operator tests using the pre-built runner). Uses linux.8xlarge.memory runners with pytest-xdist for parallel test execution.

@pytorch-bot
Copy link
Copy Markdown

pytorch-bot bot commented Apr 2, 2026

🔗 Helpful Links

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

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

❌ 1 New Failure, 2 Unrelated Failures

As of commit ca41681 with merge base e90d3c8 (image):

NEW FAILURE - The following job has failed:

BROKEN TRUNK - The following jobs 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 Apr 2, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

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.

@aliafzal aliafzal force-pushed the cadence-ci-tests branch 5 times, most recently from 93b2cbd to 1d6184a Compare April 2, 2026 21:12
@aliafzal aliafzal changed the base branch from main to cadence-runner-build-cache April 2, 2026 21:12
Base automatically changed from cadence-runner-build-cache to main April 2, 2026 21:36
@aliafzal aliafzal force-pushed the cadence-ci-tests branch 3 times, most recently from 6aa7d30 to 3a2bb8c Compare April 2, 2026 22:40
@aliafzal aliafzal added the module: cadence Issues related to the Cadence/Xtensa backend label Apr 3, 2026
@aliafzal aliafzal marked this pull request as ready for review April 3, 2026 02:29
@aliafzal aliafzal force-pushed the cadence-ci-tests branch 3 times, most recently from 7ea04a1 to 136cbd4 Compare April 3, 2026 06:02
Split Cadence CI into build and test jobs with artifact exchange.
Build job compiles cadence_runner and uploads it. Test workflow
has two parallel jobs: test-aot (Python AOT tests) and test-ops
(operator tests using the pre-built runner).
@aliafzal aliafzal changed the title Add Cadence test CI workflow Add Cadence CI test workflow with separate build and test signals Apr 3, 2026
@aliafzal aliafzal requested a review from mcremon-meta April 3, 2026 08:17
@meta-codesync
Copy link
Copy Markdown
Contributor

meta-codesync bot commented Apr 3, 2026

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

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. module: cadence Issues related to the Cadence/Xtensa backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants