gitlab: avoid timeouts in windows cross builds
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 10 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | gitlab: exclude sparc-softmmu and riscv32-softmmu from cross builds.gitlab-ci.d/ | +2 | 6 replies | |
| 2/2 | gitlab: skip many more targets in windows cross builds.gitlab-ci.d/ .gitlab-ci.d/ | +3 | 3 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Willian Rampazzo |
|---|---|
| 1/2 | R-b |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] gitlab: avoid timeouts in windows cross builds
The win64 cross build is quite often hitting the job timeout, despite having an elevated timeout of 80 minutes. A typical time is 75-78 minutes in my tests, which leaves little headroom.
I'm not inclined to increase the timeout beyond 80 minutes as this is already unreasonably long.
Interestingly the win32 job doesn't timeout in the same way. In local tests I've found the mingw32 gcc is as much as 50% faster than mingw64 gcc in building QEMU. This explains at least why we only see win64 gitlab builds timeout normally.
None the less, this series thus cuts down on the amount of stuff built in both win32 and win64 jobs, as well as cross build jobs more generally.
With this applied:
- win32 job runs in 40 minutes instead of 55 minutes
- win64 job runs in 50 minutes instead of 75 minutes
- other cross build jobs are a few minutes faster
this should give us plenty of headroom to avoid hitting the job timeouts.
Daniel P. Berrangé (2):
gitlab: exclude sparc-softmmu and riscv32-softmmu from cross builds
gitlab: skip many more targets in windows cross builds
.gitlab-ci.d/crossbuild-template.yml | 3 ++- .gitlab-ci.d/crossbuilds.yml | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-)
Signature · 1 line
2.31.1