From: "Ihor Solodrai" <ihor.solodrai@linux.dev>
To: "iii" <iii@imap.linux.ibm.com>
Cc: "Ilya Leoshkevich" <iii@linux.ibm.com>,
"Yonghong Song" <yonghong.song@linux.dev>,
"Song Liu" <song@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
bpf@vger.kernel.org, kernel-team@meta.com
Subject: Re: s390x: selftests/bpf are failing on CI
Date: Tue, 01 Apr 2025 18:23:51 +0000 [thread overview]
Message-ID: <e9b85e60b138e89ae1768e356ebee127b41498e7@linux.dev> (raw)
In-Reply-To: <1199a2932ed1800fa0a898e67ba74590@imap.linux.ibm.com>
On 4/1/25 1:06 AM, iii wrote:
> On 2025-04-01 00:45, Ihor Solodrai wrote:
>> [...]
>> A little off-topic: it looks like ebpf runners are offline again,
>> could be due to recent github runner version bump.
>
> The new docker image looks malformed:
>
> $ docker run -it --rm ghcr.io/kernel-patches/runner:main-noble-s390x
> exec /entrypoint.sh: exec format error
>
> $ docker run -it --rm --entrypoint=/bin/sh ghcr.io/kernel-patches/runner:main-noble-s390x
> # cat /entrypoint.sh
> 404: Not Found
Please make sure you're using an up-to-date image.
Link: https://github.com/kernel-patches/runner/pkgs/container/runner/385557209?tag=main-noble-s390x
Digest: sha256:946298c96c51af666f8747be3afcf9a8e59483c40cf790cd94939abf6ec22969
A malformed image was pushed on 2025-03-20, then reverted and later
updated correctly.
If you're using the same ansible setup that we do, restarting the
systemd service controlling the runners should help.
>
>>
>>>
>>> Best regards,
>>> Ilya
prev parent reply other threads:[~2025-04-01 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 18:25 s390x: selftests/bpf are failing on CI Ihor Solodrai
2025-03-31 22:45 ` Ihor Solodrai
[not found] ` <1199a2932ed1800fa0a898e67ba74590@imap.linux.ibm.com>
[not found] ` <a1b5ac5e01e50a6f3dc1047a08b725d6@imap.linux.ibm.com>
2025-04-01 15:53 ` Vasily Gorbik
2025-04-01 18:14 ` Ihor Solodrai
2025-04-01 18:23 ` Ihor Solodrai [this message]
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=e9b85e60b138e89ae1768e356ebee127b41498e7@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=iii@imap.linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=kernel-team@meta.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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