Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DISABLED test_cublas_and_lt_reduced_precision_fp16_accumulate_cuda (__main__.TestMatmulCudaCUDA) #151890

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

Open
pytorch-bot bot opened this issue Apr 22, 2025 · 4 comments · May be fixed by #153083
Open

DISABLED test_cublas_and_lt_reduced_precision_fp16_accumulate_cuda (__main__.TestMatmulCudaCUDA) #151890

pytorch-bot bot opened this issue Apr 22, 2025 · 4 comments · May be fixed by #153083
Labels
module: cublas Problem related to cublas support 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 Apr 22, 2025

Platforms: 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 3 workflow(s) with 6 failures and 3 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_cublas_and_lt_reduced_precision_fp16_accumulate_cuda
  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_matmul_cuda.py", line 183, in test_cublas_and_lt_reduced_precision_fp16_accumulate
    out = torch.baddbmm(a, b, c)
RuntimeError: CUDA error: CUBLAS_STATUS_INVALID_VALUE when calling `cublasLtMatmulAlgoGetHeuristic( ltHandle, computeDesc.descriptor(), Adesc.descriptor(), Bdesc.descriptor(), Cdesc.descriptor(), Cdesc.descriptor(), preference.descriptor(), 1, &heuristicResult, &returnedResult)`

To execute this test, run the following from the base repo dir:
    python test/test_matmul_cuda.py TestMatmulCudaCUDA.test_cublas_and_lt_reduced_precision_fp16_accumulate_cuda

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

Test file path: test_matmul_cuda.py

ResponseTimeoutError: Response timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_matmul_cuda.py 200 (connected: true, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 1)
headers: {"connection":"keep-alive","content-length":"82572","cache-control":"max-age=300","content-security-policy":"default-src 'none'; style-src 'unsafe-inline'; sandbox","content-type":"text/plain; charset=utf-8","etag":""60cdeeb596d078346db904097b9b5a15014242587f2e1a6637f974cb29443593"","strict-transport-security":"max-age=31536000","x-content-type-options":"nosniff","x-frame-options":"deny","x-xss-protection":"1; mode=block","x-github-request-id":"28E9:12A213:2598BB:30EDB3:68073AED","accept-ranges":"bytes","date":"Tue, 22 Apr 2025 06:45:03 GMT","via":"1.1 varnish","x-served-by":"cache-sjc1000103-SJC","x-cache":"MISS","x-cache-hits":"0","x-timer":"S1745304303.125742,VS0,VE193","vary":"Authorization,Accept-Encoding,Origin","access-control-allow-origin":"*","cross-origin-resource-policy":"cross-origin","x-fastly-request-id":"23f40ef721841e24aaf0fec1afdc86cbdd84d23c","expires":"Tue, 22 Apr 2025 06:50:03 GMT","source-age":"0"}

cc @clee2000 @csarofeen @ptrblck @xwang233 @eqy

@pytorch-bot pytorch-bot bot added module: flaky-tests Problem is a flaky test in CI module: unknown We do not know who is responsible for this feature, bug, or test case. skipped Denotes a (flaky) test currently skipped in CI. labels Apr 22, 2025
Copy link
Author

pytorch-bot bot commented Apr 22, 2025

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_cublas_and_lt_reduced_precision_fp16_accumulate_cuda (__main__.TestMatmulCudaCUDA)
  • Platforms for which to skip the test: linux
  • Disabled by pytorch-bot[bot]

Within ~15 minutes, test_cublas_and_lt_reduced_precision_fp16_accumulate_cuda (__main__.TestMatmulCudaCUDA) will be disabled in PyTorch CI for these platforms: 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.

How to re-enable a test

To re-enable the test globally, close the issue. To re-enable a test for only a subset of platforms, remove the platforms from the list in the issue body. This may take some time to propagate. To re-enable a test only for a PR, put Fixes #151890 in the PR body and rerun the test jobs. Note that if a test is flaky, it maybe be difficult to tell if the test is still flaky on the PR.

@bdhirsh bdhirsh added module: cublas Problem related to cublas support and removed module: unknown We do not know who is responsible for this feature, bug, or test case. labels Apr 22, 2025
@bdhirsh bdhirsh added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Apr 22, 2025
@eqy
Copy link
Collaborator

eqy commented Apr 22, 2025

CC @PaulZhang12 in case it is due to an additional output dtype

Copy link
Author

pytorch-bot bot commented May 7, 2025

Resolving the issue because the test is not flaky anymore after 1300 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 May 7, 2025
Copy link
Author

pytorch-bot bot commented May 7, 2025

Another case of trunk flakiness has been found here. Reopening issue. The list of platforms [linux] appears to contain all the recently affected platforms [linux].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: cublas Problem related to cublas support 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

Successfully merging a pull request may close this issue.

2 participants