Re: [PATCH v2 0/7] ci: some speedups for slow tests
- From
Johannes Sixt <j6t@kdbg.org>
- Date
- Nov 12, 2026, 08:19 UTC
- Message-ID
- <0182f66a-f602-4ec6-8eea-055a69f0a1c3@kdbg.org>
- In-Reply-To
- <20261109-pks-gitlab-ci-speedups-v2-0-508832602d0b@pks.im>
Am 09.11.26 um 10:58 schrieb Patrick Steinhardt:
Show 24 quoted lines
> The series contains a couple of bits that are specific to GitLab, and a > couple of fixes that are generic. Some highlights: > > - Installing the Git for Windows SDK speeds up from 3 minutes to 10 > seconds by using tar(1) instead of Extract-Archive. > > - t0027 speeds up from >10 minutes to 6 minutes on Windows by avoiding > the overhead of spawning redundant processes. > > - t5551 and t5559 both speed up by a factor of 10 on macOS, going from > 20 minutes each to 2 minutes each by using reftables in a repo with > 100k refs. "osx-meson" and "osx-clang" thus go from 29 minutes to 18 > minutes end-to-end. > > - "fedora-breaking-changes-meson" speeds up by a factor of 2, going > from 35 minutes to 16 minutes. Turns out our SHA256 implementation > is quite slow with "-O0". > > Unfortunately, our Windows runners at GitLab are still atrociously slow > by themselves. So the critical path only improves by about ~10 minutes, > going from 60-70 minutes to 53 minutes end-to-end. But hey, at least the > other jobs now give feedback a bit faster. And I guess on GitHub it may > be a different story because Windows runners are way better there and > are typically not on the critical path.
I've tested this series on my Windows notebook and it is looking good.
The runtime of t0027 went down from 4:45 to 3:14, and that of t1092 from 6:15 to 5:33. t5551 is skipped in my setup.
Thanks!
-- Hannes