- 
                Notifications
    You must be signed in to change notification settings 
- Fork 706
Revert ARM PRs fdfeaa4..4675292 #15397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…teQParam… (pytorch#15377)" This reverts commit 4675292.
This reverts commit a4e7475.
…ytorch#15378)" This reverts commit 4efd79c.
This reverts commit cf407fc.
…backend (pytorch#15369)" This reverts commit ce6b6e5.
…pytorch#15302)" This reverts commit cea66e3.
pytorch#15374)" This reverts commit 80b4a84.
…pport.py (pytorch#15373)" This reverts commit ef04360.
This reverts commit de56c81.
This reverts commit c66078c.
This reverts commit 4b42bea.
…ytorch#15352)" This reverts commit eff4024.
…rch#15364)" This reverts commit b24c39a.
This reverts commit 9075855.
…)" This reverts commit f7ca57e.
| 🔗 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 FailuresAs of commit 36f25ce with merge base cd6f2e2 ( 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. | 
| Did you miss the main PR with the issue? | 
…rch#15356)" This reverts commit fdfeaa4.
| 
 Oops, good catch. Fixed. Git hash range excluding the first got me. | 
| Thanks @GregoryComer. Added Arm folks in the review as FYI. | 
There was a problem hiding this 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
| 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. | 
| Thanks for the help @GregoryComer 🙏 | 
### 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. ```
| @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. | 
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