pytorch - 💡(How to fix) Fix DISABLED test_greencontext_stream_carveout_cuda (__main__.TestCudaGreenContextsCUDA) [2 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#181370Fetched 2026-04-25 06:02:50
View on GitHub
Comments
2
Participants
1
Timeline
18
Reactions
0
Participants
Timeline (top)
mentioned ×6subscribed ×6labeled ×4commented ×2

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, slow

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 17 workflow(s) with 34 failures and 17 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_greencontext_stream_carveout_cuda
  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_greencontext_stream_carveout_cuda in test_cuda.py is failing intermittently in CI, and debugging is required to identify the root cause.

Guidance

  • Review the recent workflow logs linked in the issue to identify patterns or common errors in the failed test runs.
  • Follow the provided debugging instructions to find relevant log snippets by grepping for test_greencontext_stream_carveout_cuda in the expanded Test step of the job.
  • Study the logs from multiple instances of the test run to understand the failure modes and potential causes.
  • Investigate the test file test_cuda.py to understand the test case and potential areas of improvement.

Notes

The issue lacks specific technical details about the failure, so a thorough review of the logs and test code is necessary to determine the root cause.

Recommendation

Apply workaround: Temporarily enable the test and run it locally or in a controlled environment to gather more information about the failure, as the CI logs may not provide enough context.

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