Repository navigation
Reduce CI timeouts #146376
Description
Activity
- added a commit that references this issue
on Mar 24, 2026 There are 26 CI jobs with timeout-minutes: 60. Presumably this is excessive for most of them and they could be reduced.
Most CI jobs are run with
--fast-ciwhich runs tests in subprocesses with a timeout per process. IMO this timeout is more important than the outer timeout of 60 minutes. Examples:- macOS:
Run 502 tests in parallel using 5 worker processes (timeout: 10 min, worker timeout: 15 min) - Ubuntu:
Run 502 tests in parallel using 6 worker processes (timeout: 10 min, worker timeout: 15 min) - WASI:
Run 502 tests in parallel using 6 worker processes (timeout: 10 min, worker timeout: 15 min) - Windows:
Run 502 tests in parallel using 6 worker processes (timeout: 10 min, worker timeout: 15 min)
--fast-cialso re-runs failing tests in verbose mode. It helps to ignore flaky tests and to get more information to debug failures.I don't think that the 60 minutes timeout is an issue in practice.
Emscripten is different because it runs tests sequentially in a single process:
Run 502 tests sequentially in a single process- macOS:
- added a commit that references this issue
on Mar 31, 2026
There are 26 CI jobs with
timeout-minutes: 60. Presumably this is excessive for most of them and they could be reduced.Requested by @webknjaz.
Linked PRs