Issue Station
Sign In
Tools hereToolbox

pytorch - 💡(How to fix) Fix DISABLED test_replicate_fully_shard_init (__main__.ReplicateFullyShardInit)

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…

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_replicate_fully_shard_init
  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/_composable/test_replicate.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

TL;DR

To resolve the flaky test issue, re-enable the test and analyze the workflow logs to identify the root cause of the failures.

Guidance

  • Re-enable the test in distributed/_composable/test_replicate.py to gather more information about the failures.
  • Follow the provided debugging instructions to find relevant log snippets in the workflow logs.
  • Study the logs from multiple instances of the test run to identify patterns or common issues that may be causing the flakiness.
  • Investigate the test's dependencies and environment to ensure that they are consistent across different runs.

Example

No specific code snippet is provided as the issue lacks detailed technical information about the test or its failures.

Notes

The provided information suggests that the test is flaky, but the root cause of the issue is unclear. Further investigation and analysis of the workflow logs are necessary to determine the cause of the failures.

Recommendation

Apply workaround: Re-enable the test and analyze the workflow logs to identify the root cause of the failures, as the issue is likely related to the test's environment or dependencies rather than a specific version issue.

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…
#training loop#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

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

Back to top recommendations

TRENDING