Skip to content

Bug fix in ExtraCUDACopy and remove unstable lints for release#82693

Closed
davidchencsl wants to merge 4 commits intogh/davidchencsl/29/basefrom
gh/davidchencsl/29/head
Closed

Bug fix in ExtraCUDACopy and remove unstable lints for release#82693
davidchencsl wants to merge 4 commits intogh/davidchencsl/29/basefrom
gh/davidchencsl/29/head

Conversation

@davidchencsl
Copy link
Contributor

@davidchencsl davidchencsl commented Aug 3, 2022

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Aug 3, 2022

🔗 Helpful links

✅ No Failures (2 Pending)

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

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


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.

davidchencsl added a commit that referenced this pull request Aug 3, 2022
@davidchencsl davidchencsl requested a review from robieta August 3, 2022 18:03
davidchencsl added a commit that referenced this pull request Aug 3, 2022
@davidchencsl
Copy link
Contributor Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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

@github-actions
Copy link
Contributor

github-actions bot commented Aug 3, 2022

Hey @davidchencsl.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

if not event.children:
return False
event = event.children[0]
if event.name() != "cudaMemcpyAsync":
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably why rocm CI was failing. Exact string matching on CUDA APIs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Thanks for pointing it out!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if event.name() != "cudaMemcpyAsync":
if event.name() not in ("cudaMemcpyAsync", "hipMemcpyWithStream"):

If you rework your PR, the above should fix ROCm CI.

@zengk95
Copy link
Contributor

zengk95 commented Aug 4, 2022

@pytorchbot revert -m 'This is breaking test_profiler_extra_cuda_copy_pattern_benchmark on windows https://hud.pytorch.org/pytorch/pytorch/commit/50a1124fd006e4d893687ce9ab1399565a9d2741' -c nosignal

@pytorchmergebot
Copy link
Collaborator

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

@pytorchmergebot
Copy link
Collaborator

@davidchencsl your PR has been successfully reverted.

pytorchmergebot added a commit that referenced this pull request Aug 4, 2022
@facebook-github-bot facebook-github-bot deleted the gh/davidchencsl/29/head branch August 7, 2022 14:18
@jeffdaily
Copy link
Collaborator

I closed the issue that skipped the failing rocm ci, pending a rework of this PR.

#82781

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants