-
Notifications
You must be signed in to change notification settings - Fork 22k
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
Comments
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:
Within ~15 minutes, 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.
We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows. |
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]. |
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 |
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:
test_cusparse_multiple_threads_same_device
Sample error message
Test file path:
test_cuda_expandable_segments.py
cc @ptrblck @msaroufim @clee2000 @ezyang @bdhirsh @anijain2305 @chauhang
The text was updated successfully, but these errors were encountered: