DISABLED test_inductor_reuse_buffer_after_inplace_collective (__main__.CompileTest) #147950
Comments
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:
Within ~15 minutes, 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. We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows. How to re-enable a testTo 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 |
|
Another case of trunk flakiness has been found here. The list of platforms [inductor] does not appear to contain all the recently affected platforms [rocm, inductor]. Adding [rocm]. |
|
Another case of trunk flakiness has been found here. The list of platforms [inductor, rocm] does not appear to contain all the recently affected platforms [linux, rocm]. Adding [linux]. |
|
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. |
|
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. |
|
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 |
|
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]. |
|
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. |
|
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. |
|
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 |
|
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]. |
|
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. |
|
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 |
|
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]. |
|
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. |
|
Resolving the issue because the test is not flaky anymore after 300 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 |
|
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]. |
|
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]. |
|
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. |
Platforms: inductor, rocm, linux
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 5 workflow(s) with 10 failures and 5 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:
test_inductor_reuse_buffer_after_inplace_collectiveTest file path:
distributed/test_c10d_functional_native.pycc @clee2000 @wdvr @chauhang @penguinwu
The text was updated successfully, but these errors were encountered: