qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cleber Rosa <crosa@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Yoshinori Sato" <ysato@users.sourceforge.jp>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	qemu-devel@nongnu.org,
	"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 3/4] tests/acceptance: Disable the rx sash and arm cubieboard replay test on Gitlab
Date: Thu, 23 Jul 2020 11:36:05 -0400 (EDT)	[thread overview]
Message-ID: <2001087850.4576521.1595518565995.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <de0c01b5-80e0-63f7-7a69-fb8f0d4b5b4c@redhat.com>


----- Thomas Huth <thuth@redhat.com> wrote:
> On 23/07/2020 14.53, Philippe Mathieu-Daudé wrote:
> > On 7/23/20 2:27 PM, Thomas Huth wrote:
> >> These tests always time out on Gitlab, not sure what's happening here.
> >> Let's disable them until somebody has enough spare time to debug the
> >> issues.
> > 
> > Is the Avocado cache working? Is it failing with an empty cache?
> > If so, maybe we need to run avocado cache fetching in a previous
> > step, before the testing job.
> > 
> > Can you share a url of failed job so I can have a look?
> 
> CentOS:
>  https://gitlab.com/huth/qemu/-/jobs/651179303
> 
I don't see the sash files being downloaded/checked ahead of test execution, so that may be an issue indeed. But for the cubieboard, that is being done, so does not look like a cache issue.

Either way, it's better to disable these and re-enable them after a proper investigation (I'll follow up with that).

Reviewed-by: Cleber Rosa <crosa@redhat.com>


> Debian:
>  https://gitlab.com/huth/qemu/-/jobs/651179296
> 
> ... might be a cache issue, indeed.
> 
>  Thomas



  reply	other threads:[~2020-07-23 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 12:27 [PATCH 0/4] Test more in less time in the Gitlab-CI Thomas Huth
2020-07-23 12:27 ` [PATCH 1/4] tests/docker: Add python3-venv and netcat to the debian-amd64 container Thomas Huth
2020-07-23 12:27 ` [PATCH 2/4] iotests: Select a default machine for the rx and avr targets Thomas Huth
2020-07-23 12:27 ` [PATCH 3/4] tests/acceptance: Disable the rx sash and arm cubieboard replay test on Gitlab Thomas Huth
2020-07-23 12:33   ` Wainer dos Santos Moschetta
2020-07-23 12:53   ` Philippe Mathieu-Daudé
2020-07-23 13:05     ` Thomas Huth
2020-07-23 15:36       ` Cleber Rosa [this message]
2020-07-23 12:28 ` [PATCH 4/4] gitlab-ci.yml: Add build-system-debian and build-system-centos jobs Thomas Huth

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=2001087850.4576521.1595518565995.JavaMail.zimbra@redhat.com \
    --to=crosa@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --cc=pavel.dovgaluk@ispras.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=ysato@users.sourceforge.jp \
    /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).