On 18/11/2024 16.32, Peter Maydell wrote:
> The current 30 minute timeout on the cross_accel_build_job template
> is a bit low: sometimes if the k8s runners are running slow the
> can hit it, for example this cross-arm64-xen-only job hit the
> 30 minute timeout while still not quite finished with the compile:
> https://gitlab.com/qemu-project/qemu/-/jobs/8401277985
>
> This is partly a "runner performance can be unpredictable" issue:
> https://gitlab.com/qemu-project/qemu/-/jobs/8391726482
> is the same job from just a day earlier and it finished in
> 16 minutes. But we already have build jobs that are higher
> timeouts than 30 minutes, so we have headroom to raise the
> timeout here to something we're less likely to hit on a slow
> runner.
>
> Bump the cross_accel_build_job timeout to 60 mins.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> .gitlab-ci.d/crossbuild-template.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitlab-ci.d/crossbuild-template.yml b/.gitlab-ci.d/crossbuild-template.yml
> index 45a98103554..303943f818f 100644
> --- a/.gitlab-ci.d/crossbuild-template.yml
> +++ b/.gitlab-ci.d/crossbuild-template.yml
> @@ -57,7 +57,7 @@
> extends: .base_job_template
> stage: build
> image: $CI_REGISTRY_IMAGE/qemu/$IMAGE:$QEMU_CI_CONTAINER_TAG
> - timeout: 30m
> + timeout: 60m
IIRC the default timeout is 60 minutes, so we could also simply drop the
line now. Anyway:
Reviewed-by: Thomas Huth <thuth@redhat.com>