-
Notifications
You must be signed in to change notification settings - Fork 379
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 scuba logging to edge API's #7103
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/7103
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 366493b with merge base a347665 (): This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This pull request was exported from Phabricator. Differential Revision: D66385141 |
Summary: Pull Request resolved: #7103 Differential Revision: D66385141
0a5ce34
to
3c97772
Compare
This pull request was exported from Phabricator. Differential Revision: D66385141 |
Summary: Adding scuba logging to the Edge AOT API's. Whenever the API's are used this will log some basic details to Scuba and also if the API call fails it will log the stack trace and the reason why it failed, to Scuba. This is only enabled for internal users and for OSS users it'll essentially be a no-op. The cases where logging is done: - User uses the API in a notebook - User uses the API via `buck run` or `buck test` on devserver Logging will not be done if the API is called via automated tests. Reviewed By: JacobSzwejbka Differential Revision: D66385141
3c97772
to
b2a0ee4
Compare
This pull request was exported from Phabricator. Differential Revision: D66385141 |
Summary: Adding scuba logging to the Edge AOT API's. Whenever the API's are used this will log some basic details to Scuba and also if the API call fails it will log the stack trace and the reason why it failed, to Scuba. This is only enabled for internal users and for OSS users it'll essentially be a no-op. The cases where logging is done: - User uses the API in a notebook - User uses the API via `buck run` or `buck test` on devserver Logging will not be done if the API is called via automated tests. Reviewed By: JacobSzwejbka Differential Revision: D66385141
b2a0ee4
to
9b0dea2
Compare
This pull request was exported from Phabricator. Differential Revision: D66385141 |
Summary: Adding scuba logging to the Edge AOT API's. Whenever the API's are used this will log some basic details to Scuba and also if the API call fails it will log the stack trace and the reason why it failed, to Scuba. This is only enabled for internal users and for OSS users it'll essentially be a no-op. The cases where logging is done: - User uses the API in a notebook - User uses the API via `buck run` or `buck test` on devserver Logging will not be done if the API is called via automated tests. Reviewed By: JacobSzwejbka Differential Revision: D66385141
9b0dea2
to
afb6f36
Compare
This pull request was exported from Phabricator. Differential Revision: D66385141 |
1 similar comment
This pull request was exported from Phabricator. Differential Revision: D66385141 |
Summary: Adding scuba logging to the Edge AOT API's. Whenever the API's are used this will log some basic details to Scuba and also if the API call fails it will log the stack trace and the reason why it failed, to Scuba. This is only enabled for internal users and for OSS users it'll essentially be a no-op. The cases where logging is done: - User uses the API in a notebook - User uses the API via `buck run` or `buck test` on devserver Logging will not be done if the API is called via automated tests. Pull Request resolved: #7103 Reviewed By: JacobSzwejbka Differential Revision: D66385141
afb6f36
to
b179e4b
Compare
Summary: Adding scuba logging to the Edge AOT API's. Whenever the API's are used this will log some basic details to Scuba and also if the API call fails it will log the stack trace and the reason why it failed, to Scuba. This is only enabled for internal users and for OSS users it'll essentially be a no-op. The cases where logging is done: - User uses the API in a notebook - User uses the API via `buck run` or `buck test` on devserver Logging will not be done if the API is called via automated tests. Pull Request resolved: #7103 Reviewed By: JacobSzwejbka Differential Revision: D66385141
b179e4b
to
0230d5f
Compare
This pull request was exported from Phabricator. Differential Revision: D66385141 |
Summary: Adding scuba logging to the Edge AOT API's. Whenever the API's are used this will log some basic details to Scuba and also if the API call fails it will log the stack trace and the reason why it failed, to Scuba. This is only enabled for internal users and for OSS users it'll essentially be a no-op. The cases where logging is done: - User uses the API in a notebook - User uses the API via `buck run` or `buck test` on devserver Logging will not be done if the API is called via automated tests. Pull Request resolved: #7103 Reviewed By: JacobSzwejbka Differential Revision: D66385141
0230d5f
to
5a051a9
Compare
This pull request was exported from Phabricator. Differential Revision: D66385141 |
Summary: Adding scuba logging to the Edge AOT API's. Whenever the API's are used this will log some basic details to Scuba and also if the API call fails it will log the stack trace and the reason why it failed, to Scuba. This is only enabled for internal users and for OSS users it'll essentially be a no-op. The cases where logging is done: - User uses the API in a notebook - User uses the API via `buck run` or `buck test` on devserver Logging will not be done if the API is called via automated tests. Reviewed By: JacobSzwejbka Differential Revision: D66385141
5a051a9
to
366493b
Compare
This pull request was exported from Phabricator. Differential Revision: D66385141 |
Differential Revision: D66385141