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

[Daniel P . Berrangé]

On Tue, Sep 12, 2023 at 03:15:28PM +0100, Daniel P. Berrangé wrote:
> On Tue, Sep 12, 2023 at 10:02:17AM -0400, Stefan Hajnoczi wrote:
> > On Tue, 12 Sept 2023 at 09:53, Daniel P. Berrangé <berrange@redhat.com> 
> > wrote:
> > >
> > > 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.
> > 
> > I'm glad you spotted that. I'm not familiar with Cirrus. Could you
> > send a patch that sets 'timeout_in'?
> 
> Yes, testing now
> 
>   
> https://gitlab.com/berrange/qemu/-/commit/c15d677de5ed2965464bc6212f049ed9785c4434
> 
>   https://gitlab.com/berrange/qemu/-/jobs/5069195895
> 
>   https://cirrus-ci.com/task/5135339078025216
> 
> The cirrus CI job page looks to be picking up the elevated timeout.

Still fails, and given it previously worked at 35 minutes, needing
a 1h30 timeout would be incredulous. This appears to be a genuine
hang in QEMU's test suite on FreeBSD 13.2.

I'm spinning up a VM to debug further

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 :|