Skip to content

Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, DeepSeek-V4.1, MiniMax-H3, Gemma 4, FLUX and more.

CI: raise the Core zoo job cap from 25 to 35 minutes (#14240)

Daniel Han4f5a98caef64
diff --git a/.github/workflows/consolidated-tests-ci.yml b/.github/workflows/consolidated-tests-ci.yml
index 1dcb6be7ec7..241eb778eb1 100644
--- a/.github/workflows/consolidated-tests-ci.yml
+++ b/.github/workflows/consolidated-tests-ci.yml
@@ -2336,11 +2336,12 @@ jobs:
trl_spec: "__from_pyproject__"
name: "Core zoo (${{ matrix.combo.label }})"
runs-on: ubuntu-24.04
- # 25 rather than `consolidated`'s 35. This job runs the ~7.6 min zoo suite
- # on top of the preamble and nothing else, and the cap is what turns a hung
- # test into a bounded failure; see PYTEST_TIMEOUT in the step below, which
- # is the mechanism that actually names the culprit.
- timeout-minutes: 25
+ # Same as `consolidated`. The zoo suite (`pytest -n 4` plus the serial files)
+ # now takes up to about 23 min on a busy runner, so a 25 min cap cancelled
+ # cells that had already passed, while the pip cache was being saved. The cap
+ # still turns a hung test into a bounded failure; PYTEST_TIMEOUT in the step
+ # below is the mechanism that actually names the culprit.
+ timeout-minutes: 35
# Same contract as `consolidated`: no job-level or per-step
# `continue-on-error`, so a failing test fails the cell.
env: