Conversation
Summary: The macOS unittest job has been hitting its timeout for several runs in a row with the progress bar frozen partway through pytest. Add `pytest-timeout` so a stuck test fails with a nodeid and per-thread stack trace, and set `faulthandler_timeout=180` so every xdist worker dumps its threads every 3 minutes while tests are still running — this surfaces the hung test as it develops, not just at termination. Drop the job timeout to 30 minutes so we can iterate quickly on this diagnostic loop. Co-Authored-By: Claude <noreply@anthropic.com>
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19864
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 3 Cancelled Jobs, 310 Pending, 3 Unclassified FailuresAs of commit eb38dd3 with merge base b903c30 ( UNCLASSIFIED FAILURES - DrCI could not classify the following jobs because the workflow did not run on the merge base. The failures may be pre-existing on trunk or introduced by this PR:
CANCELLED JOBS - The following jobs were cancelled. Please retry:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
This PR needs a
|
|
Accidental duplicate from sl pr submit after amend broke PR linkage. Real PR is #19844. |
Summary:
The macOS unittest job has been hitting its timeout for several runs in a
row with the progress bar frozen partway through pytest. Add
pytest-timeoutso a stuck test fails with a nodeid and per-thread stacktrace, and set
faulthandler_timeout=180so every xdist worker dumps itsthreads every 3 minutes while tests are still running — this surfaces the
hung test as it develops, not just at termination. Drop the job timeout to
30 minutes so we can iterate quickly on this diagnostic loop.
Co-Authored-By: Claude noreply@anthropic.com