Skip to content

Conversation

@jackzhxng
Copy link
Contributor

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 19, 2025

🔗 Helpful Links

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

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

❌ 13 New Failures, 6 Cancelled Jobs, 2 Unrelated Failures

As of commit 4739360 with merge base 7a98dd1 (image):

NEW FAILURES - The following jobs have failed:

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

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 Aug 19, 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.

jackzhxng added a commit that referenced this pull request Aug 20, 2025
Unblock trunk to advance `viable/strict`

Intermittent segmentation faults on all of the XNNPack Optimum mac
tests. Described in more detail
[here](#13530) where the
segmentation fault happens consistently, but interestingly enough this
is before the pin bump and it is only happening intermittently.
@jackzhxng
Copy link
Contributor Author

@metascroy can you take a look at the failing coreml tests?

@metascroy
Copy link
Contributor

You have failing CI jobs....looks like you need to re-base after fixing yesterday's changes?

@metascroy
Copy link
Contributor

@metascroy can you take a look at the failing coreml tests?

I think they are not coreml tests, they are the xnnpack tests. When you added the xnnpack tests, you added them to the test-huggingface-transformers-coreml job. So we should probably update the job name (if you are going to also use it for xnnpack).

The failing tests look like the ones you fixed/skipped yesterday. Maybe rebase?

@jackzhxng
Copy link
Contributor Author

Ah my bad, yes you are right. A bit confusing let me rename them.

agrima1304 pushed a commit to agrima1304/executorch that referenced this pull request Aug 26, 2025
Unblock trunk to advance `viable/strict`

Intermittent segmentation faults on all of the XNNPack Optimum mac
tests. Described in more detail
[here](pytorch#13530) where the
segmentation fault happens consistently, but interestingly enough this
is before the pin bump and it is only happening intermittently.
@jackzhxng jackzhxng merged commit d760b77 into main Aug 26, 2025
225 of 246 checks passed
@jackzhxng jackzhxng deleted the jz/bump-optimuim branch August 26, 2025 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk 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