-
Notifications
You must be signed in to change notification settings - Fork 23.3k
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
[pytorch][mobile] deprecate the LLVM-based static analyzer #68180
Conversation
Since we've open sourced the tracing-based selective build, we can deprecate the op-dependency-graph-based selective build and the static analyzer tool that produces the dependency graph. Differential Revision: [D32358467](https://our.internmc.facebook.com/intern/diff/D32358467/) **NOTE FOR REVIEWERS**: This PR has internal Facebook specific changes or comments, please review them on [Phabricator](https://our.internmc.facebook.com/intern/diff/D32358467/)! [ghstack-poisoned]
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit ab5a975 (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
CI Flow Status⚛️ CI FlowRuleset - Version:
You can add a comment to the PR and tag @pytorchbot with the following commands: # ciflow rerun, "ciflow/default" will always be added automatically
@pytorchbot ciflow rerun
# ciflow rerun with additional labels "-l <ciflow/label_name>", which is equivalent to adding these labels manually and trigger the rerun
@pytorchbot ciflow rerun -l ciflow/scheduled -l ciflow/slow For more information, please take a look at the CI Flow Wiki. |
Since we've open sourced the tracing-based selective build, we can deprecate the op-dependency-graph-based selective build and the static analyzer tool that produces the dependency graph. Differential Revision: [D32358467](https://our.internmc.facebook.com/intern/diff/D32358467/) **NOTE FOR REVIEWERS**: This PR has internal Facebook specific changes or comments, please review them on [Phabricator](https://our.internmc.facebook.com/intern/diff/D32358467/)! ghstack-source-id: 143104426 Pull Request resolved: #68180
Since we've open sourced the tracing-based selective build, we can deprecate the op-dependency-graph-based selective build and the static analyzer tool that produces the dependency graph. Differential Revision: [D32358467](https://our.internmc.facebook.com/intern/diff/D32358467/) **NOTE FOR REVIEWERS**: This PR has internal Facebook specific changes or comments, please review them on [Phabricator](https://our.internmc.facebook.com/intern/diff/D32358467/)! [ghstack-poisoned]
Pull Request resolved: #68180 Since we've open sourced the tracing-based selective build, we can deprecate the op-dependency-graph-based selective build and the static analyzer tool that produces the dependency graph. ghstack-source-id: 143108377 Differential Revision: [D32358467](https://our.internmc.facebook.com/intern/diff/D32358467/) **NOTE FOR REVIEWERS**: This PR has internal Facebook specific changes or comments, please review them on [Phabricator](https://our.internmc.facebook.com/intern/diff/D32358467/)!
@@ -26,11 +26,6 @@ retry pip install --pre torch torchvision \ | |||
# binary, and running forward pass with a real model. | |||
if [[ "$BUILD_ENVIRONMENT" == *-mobile-custom-build-static* ]]; then | |||
TEST_CUSTOM_BUILD_STATIC=1 test/mobile/custom_build/build.sh |
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.
Maybe we could change the name later. "TEST_CUSTOM_BUILD_STATIC" looks confusing that we are still doing static selective build? cc @cccclai
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.
Oh, it may be related to selective build with static dispatch.
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.
Yes, it's selective build with static dispatch. The static analyzer one is below, called "mobile-custom-build-dynamic", as it's created for dynamic dispatch.
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.
LGTM
@@ -26,11 +26,6 @@ retry pip install --pre torch torchvision \ | |||
# binary, and running forward pass with a real model. | |||
if [[ "$BUILD_ENVIRONMENT" == *-mobile-custom-build-static* ]]; then | |||
TEST_CUSTOM_BUILD_STATIC=1 test/mobile/custom_build/build.sh |
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.
Oh, it may be related to selective build with static dispatch.
This pull request has been merged in 3dc0754. |
Summary: Pull Request resolved: #68180 Since we've open sourced the tracing-based selective build, we can deprecate the op-dependency-graph-based selective build and the static analyzer tool that produces the dependency graph. ghstack-source-id: 143108377 Test Plan: CIs Reviewed By: seemethere Differential Revision: D32358467 fbshipit-source-id: c61523706b85a49361416da2230ec1b035b8b99c
Summary: Pull Request resolved: #68180 Since we've open sourced the tracing-based selective build, we can deprecate the op-dependency-graph-based selective build and the static analyzer tool that produces the dependency graph. ghstack-source-id: 143108377 Test Plan: CIs Reviewed By: seemethere Differential Revision: D32358467 fbshipit-source-id: c61523706b85a49361416da2230ec1b035b8b99c
Stack from ghstack:
Since we've open sourced the tracing-based selective build, we can deprecate the
op-dependency-graph-based selective build and the static analyzer tool that
produces the dependency graph.
Differential Revision: D32358467
NOTE FOR REVIEWERS: This PR has internal Facebook specific changes or comments, please review them on Phabricator!