From: Claudio Fontana <cfontana@suse.de>
To: Thomas Huth <thuth@redhat.com>
Cc: "Alex Bennee" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: acceptance-system-fedora and acceptance-system-centos failing sporadically with timeout?
Date: Thu, 28 Jan 2021 11:11:13 +0100 [thread overview]
Message-ID: <9bb77a1f-d904-7548-c967-9ed0cf759bbc@suse.de> (raw)
In-Reply-To: <68c85b98-6a4b-13a7-ae86-8a63013549a7@redhat.com>
On 1/28/21 11:10 AM, Thomas Huth wrote:
> On 28/01/2021 10.45, Claudio Fontana wrote:
>> Hi,
>>
>> is it just me, or is the CI sometimes failing with timeout?
>>
>> One nice feature that cirrus and travis have is the ability to relaunch one specific test,
>> do you know if there is some way to do it in gitlab too?
>>
>> I could not find it..
>>
>> Fedora:
>> https://gitlab.com/hw-claudio/qemu/-/jobs/986936506
>
> I've sent a patch for that issue just yesterday:
>
> https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg06852.html
>
>> CentOS:
>> https://gitlab.com/hw-claudio/qemu/-/jobs/980769080
>
> Never seen that one before - if you hit it again, could you please save the
> artifacts and have a look at the log file in there to see what's exactly the
> problem?
>
> Thanks
> Thomas
>
Hello Thomas,
will do!
Ciao,
Claudio
next prev parent reply other threads:[~2021-01-28 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 9:45 acceptance-system-fedora and acceptance-system-centos failing sporadically with timeout? Claudio Fontana
2021-01-28 9:50 ` Paolo Bonzini
2021-01-28 10:00 ` Claudio Fontana
2021-01-28 10:10 ` Thomas Huth
2021-01-28 10:11 ` Claudio Fontana [this message]
2021-02-05 16:43 ` Philippe Mathieu-Daudé
2021-02-05 16:49 ` Thomas Huth
2021-02-05 17:09 ` Philippe Mathieu-Daudé
2021-02-05 20:31 ` John Snow
2021-02-05 22:19 ` [Avocado-devel] " Beraldo Leal
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=9bb77a1f-d904-7548-c967-9ed0cf759bbc@suse.de \
--to=cfontana@suse.de \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).