From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH] gitlab-ci/cirrus: Increase timeout to 100 minutes
Date: Tue, 12 Sep 2023 15:15:28 +0100 [thread overview]
Message-ID: <ZQBygFxijkkQWNO/@redhat.com> (raw)
In-Reply-To: <CAJSP0QWUqry-CtrnL8hodgD6gsJGVCaY5vG5Tn5UHecZT0kQ3g@mail.gmail.com>
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.
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 :|
next prev parent reply other threads:[~2023-09-12 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 13:38 [PATCH] gitlab-ci/cirrus: Increase timeout to 100 minutes Stefan Hajnoczi
2023-09-12 13:52 ` Daniel P. Berrangé
2023-09-12 14:02 ` Stefan Hajnoczi
2023-09-12 14:15 ` Daniel P. Berrangé [this message]
2023-09-12 14:17 ` Stefan Hajnoczi
2023-09-12 16:36 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZQBygFxijkkQWNO/@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).