From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Joel Stanley" <joel@jms.id.au>,
qemu-s390x@nongnu.org, qemu-arm@nongnu.org,
"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
"Cleber Rosa" <crosa@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Laurent Vivier" <lvivier@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"John Snow" <jsnow@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: [PATCH 0/3] testing/next: s390x gitlab updates
Date: Fri, 26 Apr 2024 16:39:35 +0100 [thread overview]
Message-ID: <20240426153938.1707723-1-alex.bennee@linaro.org> (raw)
I was asked to update the custom gitlab runner from the aging 20.04 to
22.04 which has been done. However I needed to update the provisioning
scripts and clean-up some of the cruft. Sadly this doesn't seem to be
passing cleanly as we have:
- qtest-s390x/migration-test ERROR 98.94s killed by signal 6 SIGABRT
- failing TCG tests (on s390x HW)
- float_convd fails against a generated reference
- clc returns 1
There are also lots of scary DSO warnings:
BFD: warning: system-supplied DSO at 0x7fedb6479000 has a corrupt string table index
Can I leave that to the respective maintainers to investigate please
as I have a publishing deadline coming up.
Thanks,
Alex.
Alex Bennée (3):
build-environment: make some packages optional
gitlab: migrate the s390x custom machine to 22.04
gitlab: remove stale s390x-all-linux-static conf hacks
.gitlab-ci.d/custom-runners.yml | 2 +-
...20.04-s390x.yml => ubuntu-22.04-s390x.yml} | 32 +++++++++----------
scripts/ci/setup/build-environment.yml | 16 ++++++++--
3 files changed, 29 insertions(+), 21 deletions(-)
rename .gitlab-ci.d/custom-runners/{ubuntu-20.04-s390x.yml => ubuntu-22.04-s390x.yml} (80%)
--
2.39.2
next reply other threads:[~2024-04-26 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 15:39 Alex Bennée [this message]
2024-04-26 15:39 ` [PATCH 1/3] build-environment: make some packages optional Alex Bennée
2024-04-26 15:47 ` Thomas Huth
2024-04-26 15:39 ` [PATCH 2/3] gitlab: migrate the s390x custom machine to 22.04 Alex Bennée
2024-04-26 15:47 ` Thomas Huth
2024-04-26 15:39 ` [PATCH 3/3] gitlab: remove stale s390x-all-linux-static conf hacks Alex Bennée
2024-04-26 15:49 ` Thomas Huth
2024-05-04 1:17 ` [PATCH 0/3] testing/next: s390x gitlab updates Richard Henderson
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=20240426153938.1707723-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jiaxun.yang@flygoat.com \
--cc=joel@jms.id.au \
--cc=jsnow@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).