All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org,
	Wainer dos Santos Moschetta <wainersm@redhat.com>,
	Pavel Dovgalyuk <pavel.dovgaluk@ispras.ru>,
	Cleber Rosa <crosa@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] tests/acceptance: Disable tests dependent of unreliable apt.armbian.com
Date: Fri, 18 Sep 2020 06:54:43 +0200	[thread overview]
Message-ID: <20200918045443.ecedbqhkkg4c2wjq@sirius.home.kraxel.org> (raw)
In-Reply-To: <450f5b49-6309-5806-9ab2-4fad6a06e180@redhat.com>

On Thu, Sep 17, 2020 at 07:01:22PM +0200, Philippe Mathieu-Daudé wrote:
> On 9/17/20 6:53 PM, Thomas Huth wrote:
> > On 17/09/2020 18.39, Philippe Mathieu-Daudé wrote:
> >> Armbian servers are not very reliable and confused the GitLab CI
> >> users a few times this month (path updated, archives moved, and
> >> now the SSL: CERTIFICATE_VERIFY_FAILED "certificate has expired"
> >> error). Time to disable these tests.
> >> Users can still use the artifacts from the cache (or manually add
> >> them to the cache).
> >>
> >> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> >> ---
> >>  tests/acceptance/boot_linux_console.py | 10 ++++++++++
> >>  tests/acceptance/replay_kernel.py      |  2 ++
> >>  2 files changed, 12 insertions(+)
> > 
> > These failures in the Gitlab-CI are quite annoying, indeed.
> 
> I'd rather not go via this path, but since we don't save the
> artifacts cache, I can't find a better way to not block all
> the other developers using GitLab CI.

Well, we would need to cache them somewhere, either on qemu.org,
or maybe have a download job in ci which publishes them on
qemu.gitlab.io (gitlab pages).

> But I prefer we disable the tests until something better
> emerge, rather that having the developers stopping running
> these tests. So this is a quick band-aid patch.

Yep, lets disable them until we have a solution.

Acked-by: Gerd Hoffmann <kraxel@redhat.com>

take care,
  Gerd



  reply	other threads:[~2020-09-18  4:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 16:39 [PATCH] tests/acceptance: Disable tests dependent of unreliable apt.armbian.com Philippe Mathieu-Daudé
2020-09-17 16:45 ` no-reply
2020-09-17 16:53 ` Thomas Huth
2020-09-17 17:01   ` Philippe Mathieu-Daudé
2020-09-18  4:54     ` Gerd Hoffmann [this message]
2020-09-17 17:06 ` no-reply
2020-09-17 21:24 ` Willian Rampazzo
2020-09-18 11:34 ` Philippe Mathieu-Daudé
2020-09-18 17:45 ` Philippe Mathieu-Daudé

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=20200918045443.ecedbqhkkg4c2wjq@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pavel.dovgaluk@ispras.ru \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.