-
Notifications
You must be signed in to change notification settings - Fork 536
Inspector APIs page #3229
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
Inspector APIs page #3229
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/3229
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit d5ca1bb with merge base 45fd796 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
e450541
to
721b5bc
Compare
Summary: The old screenshot has outdated event block name and event names. New screenshot was taken from a recent real run. bypass-github-export-checks bypass-github-pytorch-ci-checks bypass-github-executorch-ci-checks Reviewed By: tarun292, Jack-Khuu Differential Revision: D56447799
721b5bc
to
d5ca1bb
Compare
@pytorchbot merge |
@pytorchbot merge |
@pytorchbot cherry-pick --onto release/0.2 -c docs |
@pytorchbot cherry-pick --onto release/0.2 -c docs |
I think the cherry pick bot fails on this PR because it wasn't merged properly by the bot, i.e. #3260 (comment). Here is the corresponding log https://github.com/pytorch/executorch/actions/runs/8822987799/job/24222413111, so I think this will need to be cherry pick manually. |
Differential Revision: D56447799