Skip to content
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

DISABLED test_cusparse_multiple_threads_same_device (__main__.TestCuda) #127536

Closed
pytorch-bot bot opened this issue May 30, 2024 · 3 comments
Closed

DISABLED test_cusparse_multiple_threads_same_device (__main__.TestCuda) #127536

pytorch-bot bot opened this issue May 30, 2024 · 3 comments
Labels
module: cuda Related to torch.cuda, and CUDA support in general module: flaky-tests Problem is a flaky test in CI skipped Denotes a (flaky) test currently skipped in CI. triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Comments

@pytorch-bot
Copy link

pytorch-bot bot commented May 30, 2024

Platforms: dynamo, inductor, linux

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 6 failures and 2 successes.

Debugging instructions (after clicking on the recent samples link):
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:

  1. Click on the workflow logs linked above
  2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
  3. Grep for test_cusparse_multiple_threads_same_device
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
Sample error message
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 1477, in test_cusparse_multiple_threads_same_device
    self.assertEqual(results[t].sum().item(), size * size)
RuntimeError: CUDA error: unspecified launch failure
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.


To execute this test, run the following from the base repo dir:
     python test/test_cuda_expandable_segments.py -k TestCuda.test_cusparse_multiple_threads_same_device

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

Test file path: test_cuda_expandable_segments.py

cc @ptrblck @msaroufim @clee2000 @ezyang @bdhirsh @anijain2305 @chauhang

@pytorch-bot pytorch-bot bot added module: cuda Related to torch.cuda, and CUDA support in general module: flaky-tests Problem is a flaky test in CI oncall: pt2 skipped Denotes a (flaky) test currently skipped in CI. labels May 30, 2024
Copy link
Author

pytorch-bot bot commented May 30, 2024

Hello there! From the DISABLED prefix in this issue title, it looks like you are attempting to disable a test in PyTorch CI. The information I have parsed is below:
  • Test name: test_cusparse_multiple_threads_same_device (__main__.TestCuda)
  • Platforms for which to skip the test: dynamo, inductor, linux
  • Disabled by pytorch-bot[bot]

Within ~15 minutes, test_cusparse_multiple_threads_same_device (__main__.TestCuda) will be disabled in PyTorch CI for these platforms: dynamo, inductor, linux. Please verify that your test name looks correct, e.g., test_cuda_assert_async (__main__.TestCuda).

To modify the platforms list, please include a line in the issue body, like below. The default action will disable the test for all platforms if no platforms list is specified.

Platforms: case-insensitive, list, of, platforms

We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows.

Copy link
Author

pytorch-bot bot commented Jun 3, 2024

Another case of trunk flakiness has been found here. The list of platforms [dynamo, inductor] does not appear to contain all the recently affected platforms [linux]. Adding [linux].

@pytorch-bot pytorch-bot bot removed the oncall: pt2 label Jun 3, 2024
@albanD albanD added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Jun 4, 2024
Copy link
Author

pytorch-bot bot commented Jun 20, 2024

Resolving the issue because the test is not flaky anymore after 2450 reruns without any failures and the issue hasn't been updated in 14 days. Please reopen the issue to re-disable the test if you think this is a false positive

@pytorch-bot pytorch-bot bot closed this as completed Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: cuda Related to torch.cuda, and CUDA support in general module: flaky-tests Problem is a flaky test in CI skipped Denotes a (flaky) test currently skipped in CI. triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

No branches or pull requests

1 participant