Skip to content

Conversation

@GregoryComer
Copy link
Member

Summary

Temporarily reverting #15356 and stacked Arm backend PRs due to a buck build breakage blocking code sync. Will re-land when resolved. CC @digantdesai

@pytorch-bot
Copy link

pytorch-bot bot commented Oct 27, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure, 1 Cancelled Job, 4 Unrelated Failures

As of commit 36f25ce with merge base cd6f2e2 (image):

NEW FAILURE - The following job has failed:

CANCELLED JOB - The following job was cancelled. Please retry:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

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.

@pytorch-bot pytorch-bot bot added the ci-no-td label Oct 27, 2025
@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 27, 2025
@GregoryComer GregoryComer added the release notes: none Do not include this in the release notes label Oct 27, 2025
@digantdesai
Copy link
Contributor

Did you miss the main PR with the issue?

@GregoryComer
Copy link
Member Author

GregoryComer commented Oct 27, 2025

Did you miss the main PR with the issue?

Oops, good catch. Fixed. Git hash range excluding the first got me.

@digantdesai digantdesai requested a review from ArmRyan October 27, 2025 18:42
@digantdesai
Copy link
Contributor

Thanks @GregoryComer. Added Arm folks in the review as FYI.

Copy link
Contributor

@digantdesai digantdesai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stamping to unblock the internal stack landing

@GregoryComer
Copy link
Member Author

GregoryComer commented Oct 27, 2025

Holding off on merging this as Digant is trying to resolve the Meta build issue. I'll update by EOD.

Edit: Update, still working on trying to forward fix. Will evaluate in the morning.

@zingo
Copy link
Collaborator

zingo commented Oct 27, 2025

Thanks for the help @GregoryComer 🙏
Lets see if its needed.

GregoryComer added a commit that referenced this pull request Oct 27, 2025
### Summary
Unittest jobs are dying since
#15180. I'm not entirely sure
why the jobs passed on the PR, but they are failing consistently since
on trunk. Testing a runner size bump (2xlarge -> 2xlarge.memory) to see
if that resolves it.

Example logs (from another
[PR](#15397)). Note that the
exit code (137 / SIGKILL) likely means OOM kill.
```
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
...
Process completed with exit code 137.
```
@zingo
Copy link
Collaborator

zingo commented Oct 29, 2025

@GregoryComer @digantdesai do we want to merge this to unblock?

@GregoryComer
Copy link
Member Author

@GregoryComer @digantdesai do we want to merge this to unblock?

It looks like Digant got the internal build unblocked, so I'll close this. Thanks for your patience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-td CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. release notes: none Do not include this in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants