Open pytorch-bot[bot] opened 1 year ago
Another case of trunk flakiness has been found here. Please verify the issue was opened after this instance, that the platforms list includes all of [rocm], or disable bot might not be working as expected.
Another case of trunk flakiness has been found here. Please verify the issue was opened after this instance, that the platforms list includes all of [rocm], or disable bot might not be working as expected.
Resolving the issue because the test is not flaky anymore after 700 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
Resolving the issue because the test is not flaky anymore after 700 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 [rocm] does not appear to contain all the recently affected platforms [linux]. Adding [linux].
Another case of trunk flakiness has been found here. Reopening issue. The list of platforms [rocm] does not appear to contain all the recently affected platforms [linux]. Adding [linux].
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.
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.
Resolving the issue because the test is not flaky anymore after 2450 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 [linux, rocm] appears to contain all the recently affected platforms [linux].
Another case of trunk flakiness has been found here. Reopening issue. The list of platforms [linux, rocm] appears to contain all the recently affected platforms [linux].
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.
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.
Platforms: 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 4 workflow(s) with 4 failures and 4 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_streaming_backwards_sync
Test file path:
test_cuda.py
ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_cuda.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0) headers: {}
cc @ptrblck