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é <phi...@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 <kra...@redhat.com> take care, Gerd
