pytorch - 💡(How to fix) Fix DISABLED test_round_threshold_larger_than_cached_size (__main__.TestCachingHostAllocatorConfig) [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#182261Fetched 2026-05-04 04:57:50
View on GitHub
Comments
1
Participants
1
Timeline
17
Reactions
0
Participants
Timeline (top)
mentioned ×6subscribed ×6labeled ×4commented ×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 11 workflow(s) with 22 failures and 11 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_round_threshold_larger_than_cached_size
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.

Test file path: test_cuda.py

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

cc @ptrblck @msaroufim @eqy @jerryzh168 @tinglvv @nWEIdia

extent analysis

TL;DR

The test test_round_threshold_larger_than_cached_size in test_cuda.py is likely failing due to flakiness and needs to be investigated and debugged.

Guidance

  • Investigate the workflow logs for the test by following the provided debugging instructions to identify the cause of the flakiness.
  • Study the logs for multiple instances of the test run to understand the pattern of failures and successes.
  • Check the test file test_cuda.py for any potential issues or recent changes that could be contributing to the flakiness.
  • Consider re-enabling the test and running it locally to reproduce and debug the issue.

Notes

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

Recommendation

Apply workaround: Temporarily re-enable the test and run it locally to gather more information and debug the issue, as the CI logs may not provide enough information due to the shielding of flaky tests.

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