pytorch
pytorch copied to clipboard
DISABLED test_geometric_kstest_cuda_uint8 (__main__.TestTorchDeviceTypeCUDA)
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 3 hours, it has been determined flaky in 3 workflow(s) with 3 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:
- Click on the workflow logs linked above
- Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
- Grep for
test_geometric_kstest_cuda_uint8 - There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
cc @mruberry
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_geometric_kstest_cuda_uint8 (__main__.TestTorchDeviceTypeCUDA) - Platforms for which to skip the test: linux
Within ~15 minutes, test_geometric_kstest_cuda_uint8 (__main__.TestTorchDeviceTypeCUDA) will be disabled in PyTorch CI for these platforms: linux. 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, linux, mac, macos, rocm, win, windows.
Resolving the issue because the test is not flaky anymore after 2678 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 the issue to disable. Please verify that the platforms list includes all of [linux].
Resolving the issue because the test is not flaky anymore after 2781 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 the issue to disable. Please verify that the platforms list includes all of [linux].
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 [linux], or disable bot might not be working as expected.
Resolving the issue because the test is not flaky anymore after 1300 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 the issue to disable. Please verify that the platforms list includes all of [linux].
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 [linux], or disable bot might not be working as expected.
Resolving the issue because the test is not flaky anymore after 1150 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 the issue to disable. Please verify that the platforms list includes all of [linux].
Resolving the issue because the test is not flaky anymore after 1400 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 the issue to disable. Please verify that the platforms list includes all of [linux].
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 [linux], or disable bot might not be working as expected.
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
Another case of trunk flakiness has been found here. Reopening the issue to disable. Please verify that the platforms list includes all of [linux].
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 [linux], or disable bot might not be working as expected.
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
Another case of trunk flakiness has been found here. Reopening the issue to disable. Please verify that the platforms list includes all of [inductor].
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 [inductor], or disable bot might not be working as expected.
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 the issue to disable. Please verify that the platforms list includes all of [inductor].
Resolving the issue because the test is not flaky anymore after 1850 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 the issue to disable. Please verify that the platforms list includes all of [inductor].
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 [inductor], or disable bot might not be working as expected.
Resolving the issue because the test is not flaky anymore after 2000 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 the issue to disable. Please verify that the platforms list includes all of [inductor].
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 [inductor], or disable bot might not be working as expected.
Resolving the issue because the test is not flaky anymore after 1950 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 the issue to disable. Please verify that the platforms list includes all of [inductor].