Commit a95ec22
test(integration): bump worker_initialization_timeout to 120s in CI
`TestTemplateIntegration::test_template_runs[concurrency_template.yaml]`
consistently hits the 60s `worker_initialization_timeout` in CI on
cold-start. `concurrency_template.yaml` is alphabetically first in the
parametrized lane, so it pays the full first-time-this-CI-job cost:
- Python `multiprocessing` `spawn`-mode re-import of the entire
`inference_endpoint` package per worker subprocess (transformers,
msgspec, pyzmq, etc.)
- First-time ZMQ IPC bind + connect handshake for the worker pool
- Concurrent aggregator subprocess cold-start contending for the
same small-CI-runner CPU
Subsequent templates in the same lane benefit from warm module
caches and don't approach the limit. Local Docker runs finish all 6
templates in ~40 s total (~6.5 s/template), but CI runners with less
headroom (and `spawn` vs `fork`) consistently push the first test
past 60 s.
Bump to 120 s in this test only — `_resolve_template` injects
`settings.client.worker_initialization_timeout: 120.0` into each
template before running. Production default (60 s) is unchanged.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 924be7a commit a95ec22
1 file changed
Lines changed: 11 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
223 | 223 | | |
224 | 224 | | |
225 | 225 | | |
| 226 | + | |
| 227 | + | |
| 228 | + | |
| 229 | + | |
| 230 | + | |
| 231 | + | |
| 232 | + | |
| 233 | + | |
| 234 | + | |
| 235 | + | |
| 236 | + | |
226 | 237 | | |
227 | 238 | | |
228 | 239 | | |
| |||
0 commit comments