- 
                Notifications
    
You must be signed in to change notification settings  - Fork 710
 
Add Android standalone log target #6590
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
Add Android standalone log target #6590
Conversation
          
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/6590
 Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 44529ae with merge base 8f82198 ( This comment was automatically generated by Dr. CI and updates every 15 minutes.  | 
    
| 
           This pull request was exported from Phabricator. Differential Revision: D65268257  | 
    
Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings. Differential Revision: D65268257
2b15fe5    to
    8001f63      
    Compare
  
    | 
           This pull request was exported from Phabricator. Differential Revision: D65268257  | 
    
Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings. Reviewed By: kirklandsign Differential Revision: D65268257
8001f63    to
    9c3ac51      
    Compare
  
    | 
           This pull request was exported from Phabricator. Differential Revision: D65268257  | 
    
| 
           linter and CI failure  | 
    
Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings. Reviewed By: kirklandsign Differential Revision: D65268257
9c3ac51    to
    ac27907      
    Compare
  
    | 
           @GregoryComer has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.  | 
    
Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings. Reviewed By: kirklandsign Differential Revision: D65268257
ac27907    to
    92a07e5      
    Compare
  
    | 
           @GregoryComer has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.  | 
    
Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings. Reviewed By: kirklandsign Differential Revision: D65268257
92a07e5    to
    9ab749d      
    Compare
  
    Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings. Reviewed By: kirklandsign Differential Revision: D65268257
9ab749d    to
    6d3f033      
    Compare
  
    | 
           @GregoryComer has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.  | 
    
Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings. Reviewed By: kirklandsign Differential Revision: D65268257
6d3f033    to
    2e0413a      
    Compare
  
    | 
           @GregoryComer has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.  | 
    
Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings. Test Plan: Confirmed that ET logcat logging is present in the Android ET demo app by building and running from Android Studio. Reviewed By: kirklandsign Differential Revision: D65268257 Pulled By: GregoryComer
2e0413a    to
    44529ae      
    Compare
  
    | 
           This pull request was exported from Phabricator. Differential Revision: D65268257  | 
    
Summary: Add a standalone Android log target to enable ExecuTorch logging to logcat when not using JNI bindings.
Differential Revision: D65268257