Cleanup since FEATURE_TORCH_MOBILE is always true.#55835
Cleanup since FEATURE_TORCH_MOBILE is always true.#55835ailzhang wants to merge 1 commit intogh/ailzhang/64/basefrom
Conversation
Now that #55238 is landed for a week and no complains. It seems safe to say FEATURE_TORCH_MOBILE is always true and we can do some cleanup. [ghstack-poisoned]
💊 CI failures summary and remediationsAs of commit fb92b19 (more details on the Dr. CI page): ✅ None of the CI failures appear to be your fault 💚
❄️ 1 failure tentatively classified as flakybut reruns have not yet been triggered to confirm:
|
bhosmer
left a comment
There was a problem hiding this comment.
Just to make sure I understand, the reason we think it's ok is that we've seen no build errors from the thread_local in InferenceMode.cpp that's been sitting there for a week ungated by FEATURE_TORCH_MOBILE?
BTW I think the description is pointing to the wrong PR - 55238 still has the FEATURE_TORCH_MOBILE guard in InferenceMode.cpp, but I think the one that actually landed is 55424, which doesn't.
Summary: Pull Request resolved: pytorch#55835 Now that pytorch#55238 is landed for a week and no complains. It seems safe to say FEATURE_TORCH_MOBILE is always true and we can do some cleanup. Test Plan: Imported from OSS Reviewed By: ezyang, walterddr Differential Revision: D27721284 Pulled By: ailzhang fbshipit-source-id: 4896bc5f736373d0922cfbe8eed0d16df62f0fa1
Stack from ghstack:
Now that #55424 is landed for a
week and no complains. It seems safe to say FEATURE_TORCH_MOBILE is
always true and we can do some cleanup.
Differential Revision: D27721284