pytorch - 💡(How to fix) Fix DISABLED test_dtensor_op_db_baddbmm_cpu_float32 (__main__.TestMultiThreadedDTensorOpsCPU) [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#180522Fetched 2026-04-17 08:21:53
View on GitHub
Comments
1
Participants
1
Timeline
56
Reactions
0
Participants
Timeline (top)
mentioned ×26subscribed ×26labeled ×3commented ×1

Root Cause

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

RAW_BUFFERClick to expand / collapse

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 6 hours, it has been determined flaky in 3 workflow(s) with 0 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_dtensor_op_db_baddbmm_cpu_float32
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.

Test file path: distributed/tensor/test_dtensor_ops.py

For all disabled tests (by GitHub issue), see https://hud.pytorch.org/disabled.

cc @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @pragupta @msaroufim @dcci @aditvenk @xmfan @weifengpy

extent analysis

TL;DR

To address the flaky test, investigate the logs by following the provided debugging instructions to identify the root cause of the issue.

Guidance

  • Follow the debugging instructions to find relevant log snippets: click on the workflow logs, expand the Test step, and grep for test_dtensor_op_db_baddbmm_cpu_float32.
  • Study the logs from multiple instances of the test run to understand the pattern of failures and successes.
  • Check the test file path distributed/tensor/test_dtensor_ops.py for any potential issues or areas that could be causing the flakiness.
  • Review the list of disabled tests at https://hud.pytorch.org/disabled for any related issues or patterns.

Example

No specific code snippet can be provided without further investigation, but the test file test_dtensor_ops.py should be examined for any potential issues.

Notes

The provided information suggests that the test is flaky, but the root cause is not immediately clear. Further investigation is needed to determine the cause of the issue.

Recommendation

Apply workaround: Investigate the logs and test file to identify the root cause of the flakiness, as the issue is not clearly related to a specific version or fix.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

pytorch - 💡(How to fix) Fix DISABLED test_dtensor_op_db_baddbmm_cpu_float32 (__main__.TestMultiThreadedDTensorOpsCPU) [1 comments, 1 participants]