pytorch - 💡(How to fix) Fix DISABLED test_compiled_dtensor_op_db_histc_cpu_float32 (__main__.TestCompiledDTensorOpsCPU) [3 comments, 2 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#176973Fetched 2026-04-08 00:23:26
View on GitHub
Comments
3
Participants
2
Timeline
82
Reactions
0
Timeline (top)
mentioned ×38subscribed ×38commented ×3labeled ×3

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 5 workflow(s) with 0 failures and 5 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_compiled_dtensor_op_db_histc_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

extent analysis

Fix Plan

Fix: Flaky Test

Step 1: Identify the Flaky Test

  • Locate the test file distributed/tensor/test_dtensor_ops.py and identify the specific test function test_compiled_dtensor_op_db_histc_cpu_float32.

Step 2: Analyze the Test Logs

  • Follow the debugging instructions 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.
    3. Grep for test_compiled_dtensor_op_db_histc_cpu_float32.
    4. Study the logs to understand the failure patterns.

Step 3: Implement a Retry Mechanism

  • Add a retry mechanism to the test function using a library like tenacity:
import tenacity

@tenacity.retry(wait=tenacity.wait_exponential(multiplier=1, min=4, max=10))
def test_compiled_dtensor_op_db_histc_cpu_float32():
    # test code here
  • Adjust the retry settings as needed to handle the flaky test.

Step 4: Monitor the Test

  • Keep an eye on the test's flakiness using the hud.pytorch.org dashboard.
  • Adjust the retry mechanism or the test code as needed to improve the test's reliability.

Step 5: Re-enable the Test

  • Once the test is deemed reliable, re-enable it by removing the @skip decorator or the GitHub issue label.

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_compiled_dtensor_op_db_histc_cpu_float32 (__main__.TestCompiledDTensorOpsCPU) [3 comments, 2 participants]