From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Gerd Hoffmann <kraxel@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: Thu, 17 Sep 2020 18:53:43 +0200 [thread overview]
Message-ID: <308aaf63-a9a4-256e-a29f-9d0bd1c53532@redhat.com> (raw)
In-Reply-To: <20200917163954.50514-1-philmd@redhat.com>
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.
Acked-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2020-09-17 17:00 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 [this message]
2020-09-17 17:01 ` Philippe Mathieu-Daudé
2020-09-18 4:54 ` Gerd Hoffmann
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=308aaf63-a9a4-256e-a29f-9d0bd1c53532@redhat.com \
--to=thuth@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).