pytorch icon indicating copy to clipboard operation
pytorch copied to clipboard

[Profiler][Minor] Add typed visit method to Result.

Open robieta opened this issue 3 years ago • 6 comments

Stack from ghstack (oldest at bottom):

  • #83033
  • -> #82993
  • #82992
  • #82584

Often in post processing we want to step into a specific typed context: "If X is a torch op, do Y". This PR simply adds an ergonomic way to write such cases.

Differential Revision: D38426341

robieta avatar Aug 08 '22 16:08 robieta

:link: Helpful links

:x: 1 New Failures

As of commit b98d84eb7e (more details on the Dr. CI page):

Expand to see more
  • 1/1 failures introduced in this PR

:detective: 1 new failure recognized by patterns

The following CI failures do not appear to be due to upstream breakages

See GitHub Actions build pull / linux-docs / build-docs (python) (1/1)

Step: "Unknown" (full log | diagnosis details)

2022-08-20T07:56:11.5777598Z ##[error]The operation was canceled.
2022-08-20T02:02:05.5225103Z copying images... [ 97%] _static/img/tensorboard/add_images.png
2022-08-20T02:02:05.5226958Z copying images... [100%] _static/img/tensorboard/add_hparam.png
2022-08-20T02:02:05.5228396Z 
2022-08-20T02:02:05.5458979Z copying static files... done
2022-08-20T02:02:05.5459624Z copying extra files... done
2022-08-20T02:02:05.9691155Z dumping search index in English (code: en)... done
2022-08-20T02:02:06.0729670Z dumping object inventory... done
2022-08-20T02:02:06.0732529Z build succeeded.
2022-08-20T02:02:06.0734150Z 
2022-08-20T02:02:06.0734470Z The HTML pages are in build/html.
2022-08-20T07:56:11.5777598Z ##[error]The operation was canceled.
2022-08-20T07:56:11.5798676Z Prepare all required actions
2022-08-20T07:56:11.5814758Z ##[group]Run ./.github/actions/chown-workspace
2022-08-20T07:56:11.5814973Z ##[endgroup]
2022-08-20T07:56:11.5836962Z ##[group]Run docker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .
2022-08-20T07:56:11.5837302Z [36;1mdocker run --rm -v "$(pwd)":/v -w /v "${ALPINE_IMAGE}" chown -R "$(id -u):$(id -g)" .[0m
2022-08-20T07:56:11.5847378Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-08-20T07:56:11.5847583Z env:
2022-08-20T07:56:11.5847817Z   ALPINE_IMAGE: 308535385114.dkr.ecr.us-east-1.amazonaws.com/tool/alpine
2022-08-20T07:56:11.5848060Z ##[endgroup]
2022-08-20T07:56:13.0698428Z Post job cleanup.

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

facebook-github-bot avatar Aug 08 '22 16:08 facebook-github-bot

@pytorchbot merge -l

robieta avatar Aug 08 '22 23:08 robieta

@pytorchbot successfully started a merge and created land time checks. See merge status here and land check progress here.

pytorchmergebot avatar Aug 08 '22 23:08 pytorchmergebot

Merge failed due to Refusing to merge as mandatory check(s) pull failed for rule superuser Raised by https://github.com/pytorch/pytorch/actions/runs/2821700754 If you believe this is an error, you can use the old behavior with @pytorchbot merge -g (optionally with the "ciflow/trunk" to get land signals) or use @pytorchbot merge -f "some reason here". For more information, see the bot wiki.

pytorchmergebot avatar Aug 09 '22 03:08 pytorchmergebot

@pytorchbot merge -l

robieta avatar Aug 10 '22 00:08 robieta

Merge failed due to Refusing to merge as mandatory check(s) pull are pending/not yet run for rule superuser Raised by https://github.com/pytorch/pytorch/actions/runs/2829186158 If you believe this is an error, you can use the old behavior with @pytorchbot merge -g (optionally with the "ciflow/trunk" to get land signals) or use @pytorchbot merge -f "some reason here". For more information, see the bot wiki.

pytorchmergebot avatar Aug 10 '22 00:08 pytorchmergebot

@pytorchbot merge -g

robieta avatar Aug 10 '22 06:08 robieta

@pytorchbot merge

robieta avatar Aug 10 '22 16:08 robieta

@pytorchbot successfully started a merge job. Check the current status here

pytorchmergebot avatar Aug 10 '22 16:08 pytorchmergebot

Merge failed due to Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x d3d2bd1f1a1830fdf00fb273ffd2d7f14cb4a336 returned non-zero exit code 1

Auto-merging torch/csrc/autograd/init.cpp
CONFLICT (content): Merge conflict in torch/csrc/autograd/init.cpp
error: could not apply d3d2bd1f1a... [Profiler] Start moving python bindings out of autograd
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

Raised by https://github.com/pytorch/pytorch/actions/runs/2834024571

pytorchmergebot avatar Aug 10 '22 16:08 pytorchmergebot

@pytorchbot merge -l

robieta avatar Aug 18 '22 22:08 robieta

@pytorchbot successfully started a merge job. Check the current status here. The merge job was triggered with the land checks (-l) flag. If you did not specify this flag yourself, you are likely enrolled in the land checks rollout. This means that your change will be merged once all checks on your PR have passed since you have added the ciflow/trunk label to your PR (ETA 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki. Please reach out to the PyTorch DevX Team with feedback or questions!

pytorchmergebot avatar Aug 18 '22 22:08 pytorchmergebot

Merge failed Reason: 2 additional jobs have failed, first few of them are: trunk ,trunk / linux-bionic-cuda10.2-py3.9-gcc7 / test (default, 1, 4, linux.4xlarge.nvidia.gpu) Raised by https://github.com/pytorch/pytorch/actions/runs/2885882594 If you believe this is an error, you can use the old behavior with @pytorchbot merge -g (optionally with the ciflow/trunk to get land checks) or use @pytorchbot merge -f "some reason here". For more information, see the bot wiki. Please reach out to the PyTorch DevX Team with feedback or questions!

pytorchmergebot avatar Aug 18 '22 23:08 pytorchmergebot

@pytorchbot merge -l

robieta avatar Aug 19 '22 15:08 robieta

@pytorchbot successfully started a merge job. Check the current status here. The merge job was triggered with the land checks (-l) flag. If you did not specify this flag yourself, you are likely enrolled in the land checks rollout. This means that your change will be merged once all checks on your PR have passed since you have added the ciflow/trunk label to your PR (ETA 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki. Please reach out to the PyTorch DevX Team with feedback or questions!

pytorchmergebot avatar Aug 19 '22 15:08 pytorchmergebot

Merge failed Reason: Refusing to merge as mandatory check(s) pull failed for rule superuser Raised by https://github.com/pytorch/pytorch/actions/runs/2890373603 If you believe this is an error, you can use the old behavior with @pytorchbot merge -g (optionally with the ciflow/trunk to get land checks) or use @pytorchbot merge -f "some reason here". For more information, see the bot wiki. Please reach out to the PyTorch DevX Team with feedback or questions!

pytorchmergebot avatar Aug 19 '22 15:08 pytorchmergebot