8000 DISABLED test_reduce_stress_cuda (__main__.ProcessGroupGlooLazyInitTest) · Issue #152201 · pytorch/pytorch · GitHub
[go: up one dir, main page]
Skip to content

DISABLED test_reduce_stress_cuda (__main__.ProcessGroupGlooLazyInitTest) #152201

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.

Sign up for GitHub

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

Jump to bottom
Open
jithunnair-amd opened this issue Apr 25, 2025 · 2 comments
Open

DISABLED test_reduce_stress_cuda (__main__.ProcessGroupGlooLazyInitTest) #152201

jithunnair-amd opened this issue Apr 25, 2025 · 2 comments
Labels
module: rocm AMD GPU support for Pytorch 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

@jithunnair-amd
Copy link
Collaborator
jithunnair-amd commented Apr 25, 2025 •
edited by pytorch-bot bot
Loading

Platforms: rocm

This test was disabled because it failed on the MI300 runners in 151368: https://github.com/pytorch/pytorch/actions/runs/14502441175/job/40686794743

The stress_cuda tests seem to be flaky.

cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd
@pytorch-bot pytorch-bot bot added the skipped Denotes a (flaky) test currently skipped in CI. label Apr 25, 2025
@pytorch-bot PyTorch Bot
Copy link
pytorch-bot bot commented Apr 25, 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_reduce_stress_cuda (__main__.ProcessGroupGlooLazyInitTest)
  • Platforms for which to skip the test: rocm
  • Disabled by jithunnair-amd

Within ~15 minutes, test_reduce_stress_cuda (__main__.ProcessGroupGlooLazyInitTest) will be disabled in PyTorch CI for these platforms: 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 #152201 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.

@pytorch-bot pytorch-bot bot added the module: rocm AMD GPU support for Pytorch label Apr 25, 2025
@malfet malfet added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Apr 25, 2025
@pytorch-bot PyTorch Bot
Copy link
pytorch-bot bot commented May 14, 2025

Resolving the issue because the test is not flaky anymore after 1350 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
module: rocm AMD GPU support for Pytorch 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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@malfet @jithunnair-amd
0