-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Closed
Labels
largeWe think that this is a pretty chunky piece of workWe think that this is a pretty chunky piece of workmodule: cudaRelated to torch.cuda, and CUDA support in generalRelated to torch.cuda, and CUDA support in generalmodule: testsIssues related to tests (not the torch.testing module)Issues related to tests (not the torch.testing module)triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Description
In @fbhuba PR #21474 we switch the stream before running tests. But in this PR, a lot of tests failed and we had to disable the stream switching behavior for large portions of the test suite. There is probably something very important in PyTorch that is not stream safe, we need to figure it out.
Currently known reasons why you might be on wrong stream:
- Calling thrust functions (e.g.,
thrust::tabulate) without specifying a policy that puts things on the right stream - Backwards runs on default stream
Metadata
Metadata
Assignees
Labels
largeWe think that this is a pretty chunky piece of workWe think that this is a pretty chunky piece of workmodule: cudaRelated to torch.cuda, and CUDA support in generalRelated to torch.cuda, and CUDA support in generalmodule: testsIssues related to tests (not the torch.testing module)Issues related to tests (not the torch.testing module)triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module