DISABLED test_cache_guard (__main__.TestFxGraphCache)

[pytorch-bot[bot]]

Platforms: asan, linux, mac, macos

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 57 workflow(s) with 171 failures and 57 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_cache_guard
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 "inductor/test_codecache.py", line 113, in setUp PatchCaches.setUp() File "/var/lib/jenkins/workspace/test/inductor/mock_cache.py", line 190, in setUp if not _has_redis(): File "/var/lib/jenkins/workspace/test/inductor/mock_cache.py", line 137, in _has_redis return importlib.util.find_spec("redis") is not None File "/opt/conda/envs/py_3.8/lib/python3.8/importlib/util.py", line 111, in find_spec raise ValueError('{}.__spec__ is not set'.format(name)) from None ValueError: redis.__spec__ is not set ```

Test file path: inductor/test_codecache.py

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/inductor/test_codecache.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0) headers: {}

cc @clee2000 @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire

[pytorch-bot[bot]]

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_cache_guard (__main__.TestFxGraphCache)` * Platforms for which to skip the test: asan, linux, mac, macos * Disabled by `pytorch-bot[bot]` Within ~15 minutes, `test_cache_guard (__main__.TestFxGraphCache)` will be disabled in PyTorch CI for these platforms: asan, linux, mac, macos. 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 #133908` 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[bot]]

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

[pytorch-bot[bot]]

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

[pytorch-bot[bot]]

Resolving the issue because the test is not flaky anymore after 3705 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