Daniel P. Berrangé <berra...@redhat.com> writes:
> Perhaps the most painful of all the GitLab CI failures we see are > the enforced job timeouts: > > "ERROR: Job failed: execution took longer than 1h15m0s seconds" > > https://gitlab.com/qemu-project/qemu/-/jobs/4387047648 > > when that hits the CI log shows what has *already* run, but figuring > out what was currently running (or rather stuck) is an horrendously > difficult. I had this in my tree but I see there are a number of review comments to take into account. Will there be a v3 and do we want it this late in the cycle? -- Alex Bennée Virtualisation Tech Lead @ Linaro
