8000 DISABLED test_inductor_all_gather_into_tensor_coalesced (__main__.CompileTest) · Issue #146806 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

DISABLED test_inductor_all_gather_into_tensor_coalesced (__main__.CompileTest) #146806

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pytorch-bot bot open 8000 ed this issue Feb 10, 2025 · 89 comments
Open
Labels
module: c10d Issues/PRs related to collective communications and process groups module: flaky-tests Problem is a flaky test in CI skipped Denotes a (flaky) test currently skipped in CI. triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Comments

@pytorch-bot
Copy link
pytorch-bot bot commented Feb 10, 2025

Platforms: linux, rocm, inductor

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

Over the past 3 hours, it has been determined flaky in 7 workflow(s) with 14 failures and 7 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_inductor_all_gather_into_tensor_coalesced
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
Sample error message
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/distributed/test_c10d_functional_native.py", line 647, in setUp
    dist.init_process_group(
    ~~~~~~~~~~~~~~~~~~~~~~~^
        backend="fake",
        ^^^^^^^^^^^^^^^
    ...<2 lines>...
        store=store,
        ^^^^^^^^^^^^
    )
    ^
  File "/opt/conda/envs/py_3.13/lib/python3.13/site-packages/torch/distributed/c10d_logger.py", line 81, in wrapper
    return func(*args, **kwargs)
  File "/opt/conda/envs/py_3.13/lib/python3.13/site-packages/torch/distributed/c10d_logger.py", line 95, in wrapper
    func_return = func(*args, **kwargs)
  File "/opt/conda/envs/py_3.13/lib/python3.13/site-packages/torch/distributed/distributed_c10d.py", line 1637, in init_process_group
    raise ValueError("trying to initialize the default process group twice!")
ValueError: trying to initialize the default process group twice!

Test file path: distributed/test_c10d_functional_native.py

cc @clee2000 @wdvr

@pytorch-bot pytorch-bot bot added module: c10d Issues/PRs related to collective communications and process groups module: flaky-tests Problem is a flaky test in CI skipped Denotes a (flaky) test currently skipped in CI. triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module labels Feb 10, 2025
Copy link
Author
pytorch-bot bot commented Feb 10, 2025
Hello there! From the DISABLED prefix in this issue title, it looks like you are attempting to disable a test in PyTorch CI. The information I have parsed is below:
  • Test name: test_inductor_all_gather_into_tensor_coalesced (__main__.CompileTest)
  • Platforms for which to skip the test: inductor, linux, rocm
  • Disabled by pytorch-bot[bot]

Within ~15 minutes, test_inductor_all_gather_into_tensor_coalesced (__main__.CompileTest) will be disabled in PyTorch CI for these platforms: inductor, linux, rocm. Please verify that your test name looks correct, e.g., test_cuda_assert_async (__main__.TestCuda).

To modify the platforms list, please include a line in the issue body, like below. The default action will disable the test for all platforms if no platforms list is specified.

Platforms: case-insensitive, list, of, platforms

We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows.

How to re-enable a test

To re-enable the test globally, close the issue. To re-enable a test for only a subset of platforms, remove the platforms from the list in the issue body. This may take some time to propagate. To re-enable a test only for a PR, put Fixes #146806 in the PR body and rerun the test jobs. Note that if a test is flaky, it maybe be difficult to tell if the test is still flaky on the PR.

Copy link
Author
pytorch-bot bot commented Feb 10, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 10, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 10, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 10, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 10, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 12, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 12, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux] does not appear to contain all the recently affected platforms [linux, rocm]. Adding [rocm].

Copy link
Author
pytorch-bot bot commented Feb 12, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 12, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 12, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 12, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 13, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 13, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 13, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 13, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 13, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 13, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 13, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 13, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 14, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 14, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 14, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 14, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 14, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Feb 14, 2025

Another case of trunk flakiness has been found here. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

@pytorch-bot pytorch-bot bot reopened this Mar 4, 2025
Copy link
Author
pytorch-bot bot commented Mar 4, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Mar 18, 2025

Resolving the issue because the test is not flaky anymore after 210 reruns without any failures and the issue hasn't been updated in 14 days. Please reopen the issue to re-disable the test if you think this is a false positive

@pytorch-bot pytorch-bot bot closed this as completed Mar 18, 2025
Copy link
Author
pytorch-bot bot commented Mar 19, 2025

Another case of trunk flakiness has been found here. Reopening issue. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [inductor].

@pytorch-bot pytorch-bot bot reopened this Mar 19, 2025
Copy link
Author
pytorch-bot bot commented Mar 19, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Mar 19, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Apr 2, 2025

Resolving the issue because the test is not flaky anymore after 240 reruns without any failures and the issue hasn't been updated in 14 days. Please reopen the issue to re-disable the test if you think this is a false positive

@pytorch-bot pytorch-bot bot closed this as completed Apr 2, 2025
Copy link
Author
pytorch-bot bot commented Apr 2, 2025

Another case of trunk flakiness has been found here. Reopening issue. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux].

@pytorch-bot pytorch-bot bot reopened this Apr 2, 2025
Copy link
Author
pytorch-bot bot commented Apr 2, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Apr 16, 2025

Resolving the issue because the test is not flaky anymore after 210 reruns without any failures and the issue hasn't been updated in 14 days. Please reopen the issue to re-disable the test if you think this is a false positive

@pytorch-bot pytorch-bot bot closed this as completed Apr 16, 2025
Copy link
Author
pytorch-bot bot commented Apr 16, 2025

Another case of trunk flakiness has been found here. Reopening issue. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [inductor].

@pytorch-bot pytorch-bot bot reopened this Apr 16, 2025
Copy link
Author
pytorch-bot bot commented Apr 16, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented Apr 16, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
F438
Author
pytorch-bot bot commented Apr 30, 2025

Resolving the issue because the test is not flaky anymore after 315 reruns without any failures and the issue hasn't been updated in 14 days. Please reopen the issue to re-disable the test if you think this is a false positive

@pytorch-bot pytorch-bot bot closed this as completed Apr 30, 2025
Copy link
Author
pytorch-bot bot commented Apr 30, 2025

Another case of trunk flakiness has been found here. Reopening issue. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux, rocm].

@pytorch-bot pytorch-bot bot reopened this Apr 30, 2025
Copy link
Author
pytorch-bot bot commented Apr 30, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux, rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented May 1, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Copy link
Author
pytorch-bot bot commented May 14, 2025

Resolving the issue because the test is not flaky anymore after 315 reruns without any failures and the issue hasn't been updated in 14 days. Please reopen the issue to re-disable the test if you think this is a false positive

@pytorch-bot pytorch-bot bot closed this as completed May 14, 2025
Copy link
Author
pytorch-bot bot commented May 15, 2025

Another case of trunk flakiness has been found here. Reopening issue. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [inductor].

@pytorch-bot pytorch-bot bot reopened this May 15, 2025
Copy link
Author
pytorch-bot bot commented May 15, 2025

Another case of trunk flakiness has been found here. The list of platforms [inductor, linux, rocm] appears to contain all the recently affected platforms [linux]. Either the change didn't propogate fast enough or disable bot might be broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: c10d Issues/PRs related to collective communications and process groups module: flaky-tests Problem is a flaky test in CI skipped Denotes a (flaky) test currently skipped in CI. triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

No branches or pull requests

0 participants
0