-
Notifications
You must be signed in to change notification settings - Fork 536
Use etdump gen instead of event tracer #8968
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
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/8968
Note: Links to docs will display an error until the docs builds have been completed. ❌ 19 New Failures, 1 Cancelled JobAs of commit 9cd99e9 with merge base 73acde9 ( NEW FAILURES - The following jobs have failed:
CANCELLED JOB - The following job was cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
This pull request was exported from Phabricator. Differential Revision: D70356526 |
3f4740a
to
caed8b7
Compare
Summary: Use an actual event tracer implementation - ETDumpGen, so we can do profiling and logging in module base class Differential Revision: D70356526
This pull request was exported from Phabricator. Differential Revision: D70356526 |
Summary: Pull Request resolved: pytorch#8968 Use an actual event tracer implementation - ETDumpGen, so we can do profiling and logging in module base class Differential Revision: D70356526
caed8b7
to
d9fba31
Compare
Summary: Use an actual event tracer implementation - ETDumpGen, so we can do profiling and logging in module base class Differential Revision: D70356526
d9fba31
to
9cd99e9
Compare
This pull request was exported from Phabricator. Differential Revision: D70356526 |
Differential Revision: D70356526