-
Notifications
You must be signed in to change notification settings - Fork 537
Depend on extension/threadpool, not thread_parallel_interface, in buck #9511
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
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/9511
Note: Links to docs will display an error until the docs builds have been completed. ❌ 1 New FailureAs of commit a405ce1 with merge base 90f0843 ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
I planned to do this everywhere and forgot. Clean it all up, leave a note, enforce the note with visibility. This makes sure everything in buck-land gets ET_USE_THREADPOOL. Test Plan: Profiled run on internal model, no longer seeing parallel_for_no_threadpool ghstack-source-id: e371f0b ghstack-comment-id: 2744624045 Pull Request resolved: #9511
unittest-buck / macos is having problems on main. (#9505 is out to fix them.) I ran unittest-buck2.sh locally on mac and verified it passed. |
I planned to do this everywhere and forgot. Clean it all up, leave a note, enforce the note with visibility. This makes sure everything in buck-land gets ET_USE_THREADPOOL. Test Plan: Profiled run on internal model, no longer seeing parallel_for_no_threadpool ghstack-source-id: 4495656 ghstack-comment-id: 2744624045 Pull Request resolved: #9511
ping reviewers @JacobSzwejbka @manuelcandales @kimishpatel @lucylq |
…e, in buck (#9511)" Trying again with internal fixes. Original summary: I planned to do this everywhere and forgot. Clean it all up, leave a note, enforce the note with visibility. This makes sure everything in buck-land gets ET_USE_THREADPOOL. Differential Revision: [D72090889](https://our.internmc.facebook.com/intern/diff/D72090889/) [ghstack-poisoned]
…e, in buck (#9511)" Trying again with internal fixes. Original summary: I planned to do this everywhere and forgot. Clean it all up, leave a note, enforce the note with visibility. This makes sure everything in buck-land gets ET_USE_THREADPOOL. Differential Revision: [D72090889](https://our.internmc.facebook.com/intern/diff/D72090889/) ghstack-source-id: 276012372 Pull Request resolved: #9890
…adpool, not thread_parallel_interface, in buck (#9511)"" Trying again with internal fixes. Original summary: I planned to do this everywhere and forgot. Clean it all up, leave a note, enforce the note with visibility. This makes sure everything in buck-land gets ET_USE_THREADPOOL. Differential Revision: [D72090889](https://our.internmc.facebook.com/intern/diff/D72090889/) [ghstack-poisoned]
…e, in buck (#9511)" Pull Request resolved: #9890 Trying again with internal fixes. Original summary: I planned to do this everywhere and forgot. Clean it all up, leave a note, enforce the note with visibility. This makes sure everything in buck-land gets ET_USE_THREADPOOL. Differential Revision: [D72090889](https://our.internmc.facebook.com/intern/diff/D72090889/) ghstack-source-id: 276017129
#9511) I planned to do this everywhere and forgot. Clean it all up, leave a note, enforce the note with visibility. This makes sure everything in buck-land gets ET_USE_THREADPOOL. Test Plan: Profiled run on internal model, no longer seeing parallel_for_no_threadpool
I planned to do this everywhere and forgot. Clean it all up, leave a note, enforce the note with visibility. This makes sure everything in buck-land gets ET_USE_THREADPOOL.
Test Plan: Profiled run on internal model, no longer seeing parallel_for_no_threadpool