Re: [PATCH] gitlab-ci/cirrus: Increase timeout to 100 minutes

["Daniel P. Berrangé" <berrange@redhat.com>]

On Tue, Sep 12, 2023 at 09:38:29AM -0400, Stefan Hajnoczi wrote:
> The 80m timeout is not enough:
> 
>   672/832 qemu:block / io-qcow2-041          OK             39.77s   1 subtests passed
>   Timed out!

IIUC, that 'timed out' message is coming from Cirrus CI logs, which
we can see over on the cirrus task:

  https://cirrus-ci.com/task/6462328380588032

> https://gitlab.com/qemu-project/qemu/-/jobs/5058610599

This reports duration "64 minutes", vs a GitLab timeout of 1hr20.

IOW, we're not hitting the gitlab timeout, we're hitting hte
Cirrus CI timeout, which defaults to 60 minutes.  The other
4 minuts gitlab reports is likely because Cirrus queued the
job for 4 minutes before starting execution.

> 
> Buglink: https://gitlab.com/qemu-project/qemu/-/issues/1882
> Fixes: d06f3bf92267 ("gitlab-ci/cirrus: Increase timeout to 80 minutes")
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>  .gitlab-ci.d/cirrus.yml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/.gitlab-ci.d/cirrus.yml b/.gitlab-ci.d/cirrus.yml
> index 41d64d6680..d19633f758 100644
> --- a/.gitlab-ci.d/cirrus.yml
> +++ b/.gitlab-ci.d/cirrus.yml
> @@ -15,7 +15,7 @@
>    stage: build
>    image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:master
>    needs: []
> -  timeout: 80m
> +  timeout: 100m
>    allow_failure: true
>    script:
>      - source .gitlab-ci.d/cirrus/$NAME.vars

IIUC, we need to put a 'timeout_in' setting someone in
.gitlab-ci.d/cirrus/build.yml instead, to override
Cirrus 60 minute limit:

https://cirrus-ci.org/faq/#instance-timed-out


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|