Issue Station
Sign In
Tools hereToolbox

pytorch - 💡(How to fix) Fix DISABLED test_quiesce (__main__.TestCompileWorker) [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#181080•Fetched 2026-04-23 07:22:51
View on GitHub
Comments
1
Participants
1
Timeline
114
Reactions
0
Author
pytorch-bot[bot]pytorch-bot[bot]
Participants
pytorch-bot[bot]pytorch-bot[bot]
Timeline (top)
mentioned ×54subscribed ×54labeled ×5commented ×1

Error Message

Traceback (most recent call last): File "/var/lib/jenkins/workspace/test/inductor/test_compile_worker.py", line 74, in test_quiesce pool.shutdown() File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_inductor/compile_worker/subproc_pool.py", line 342, in shutdown self.process.wait(300) File "/opt/conda/envs/py_3.10/lib/python3.10/subprocess.py", line 1209, in wait return self._wait(timeout=timeout) File "/opt/conda/envs/py_3.10/lib/python3.10/subprocess.py", line 1951, in _wait raise TimeoutExpired(self.args, timeout) subprocess.TimeoutExpired: Command '['/opt/conda/envs/py_3.10/bin/python', '/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_inductor/compile_worker/main.py', '--pickler=torch._inductor.compile_worker.subproc_pool.SubprocPickler', '--kind=fork', '--workers=2', '--parent=48264', '--read-fd=9', '--write-fd=16', '--torch-key=CH8GIdr0ls34lJVkMgiQUDdQP0vdz42TDNvYUdyqSng=']' timed out after 300 seconds

Root Cause

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

Code Example

Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/inductor/test_compile_worker.py", line 74, in test_quiesce
    pool.shutdown()
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_inductor/compile_worker/subproc_pool.py", line 342, in shutdown
    self.process.wait(300)
  File "/opt/conda/envs/py_3.10/lib/python3.10/subprocess.py", line 1209, in wait
    return self._wait(timeout=timeout)
  File "/opt/conda/envs/py_3.10/lib/python3.10/subprocess.py", line 1951, in _wait
    raise TimeoutExpired(self.args, timeout)
subprocess.TimeoutExpired: Command '['/opt/conda/envs/py_3.10/bin/python', '/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_inductor/compile_worker/__main__.py', '--pickler=torch._inductor.compile_worker.subproc_pool.SubprocPickler', '--kind=fork', '--workers=2', '--parent=48264', '--read-fd=9', '--write-fd=16', '--torch-key=CH8GIdr0ls34lJVkMgiQUDdQP0vdz42TDNvYUdyqSng=']' timed out after 300 seconds
RAW_BUFFERClick to expand / collapse

Platforms: asan, linux

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

Over the past 6 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:

  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_quiesce
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
<details><summary>Sample error message</summary> 
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/inductor/test_compile_worker.py", line 74, in test_quiesce
    pool.shutdown()
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_inductor/compile_worker/subproc_pool.py", line 342, in shutdown
    self.process.wait(300)
  File "/opt/conda/envs/py_3.10/lib/python3.10/subprocess.py", line 1209, in wait
    return self._wait(timeout=timeout)
  File "/opt/conda/envs/py_3.10/lib/python3.10/subprocess.py", line 1951, in _wait
    raise TimeoutExpired(self.args, timeout)
subprocess.TimeoutExpired: Command '['/opt/conda/envs/py_3.10/bin/python', '/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_inductor/compile_worker/__main__.py', '--pickler=torch._inductor.compile_worker.subproc_pool.SubprocPickler', '--kind=fork', '--workers=2', '--parent=48264', '--read-fd=9', '--write-fd=16', '--torch-key=CH8GIdr0ls34lJVkMgiQUDdQP0vdz42TDNvYUdyqSng=']' timed out after 300 seconds
</details>

Test file path: inductor/test_compile_worker.py

For all disabled tests (by GitHub issue), see https://hud.pytorch.org/disabled.

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @kadeng @muchulee8 @amjames @chauhang @aakhundov @coconutruben @jataylo

extent analysis

TL;DR

The most likely fix for the failing test is to investigate and resolve the subprocess timeout issue in the test_quiesce test.

Guidance

  • Investigate the test_quiesce test in inductor/test_compile_worker.py to understand why the subprocess is timing out after 300 seconds.
  • Review the workflow logs linked in the issue to find relevant log snippets by grepping for test_quiesce.
  • Consider increasing the timeout value or optimizing the subprocess to complete within the current timeout.
  • Study the logs from the multiple instances of the test run in CI to identify any patterns or clues that may help resolve the issue.

Notes

The provided information suggests that the test is flaky and has been disabled due to frequent failures. The subprocess timeout error may be related to the test's implementation or the environment in which it is running.

Recommendation

Apply a workaround by investigating and optimizing the subprocess to prevent timeouts, as the root cause of the issue is not immediately clear.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#database connection#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING