From: "Ihor Solodrai" <ihor.solodrai@linux.dev>
To: "Ilya Leoshkevich" <iii@linux.ibm.com>
Cc: "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: Mon, 31 Mar 2025 22:45:01 +0000 [thread overview]
Message-ID: <7d55acbf6e6b20f9e8d679883c1e77391e80b304@linux.dev> (raw)
In-Reply-To: <7adb418e282468fcd5dc10c05790614e622579d4@linux.dev>
On 3/31/25 3:25 PM, iii wrote:
> On 2025-03-31 20:25, Ihor Solodrai wrote:
>> Hi Ilya,
>>
>> After recent merges from upstream, CI started failing both on bpf and
>> bpf-next trees. Yonghong Song and Song Liu submitted a couple of fixes
>> that are already applied to bpf tree, but there are still failures on
>> s390x.
>>
>> https://github.com/kernel-patches/bpf/actions/runs/14163772245
>>
>> Could you please investigate?
>>
>> [...]
>
> Hi Ihor,
>
> Thanks for the heads up.
> I tried this manually with the kernel commit 07be1f644ff9 and the tests are passing:
>
> # ./test_progs -t attach_probe
>
> #12/1 attach_probe/manual-default:OK
> #12/2 attach_probe/manual-legacy:OK
> #12/3 attach_probe/manual-perf:OK
> #12/4 attach_probe/manual-link:OK
> #12/5 attach_probe/auto:OK
> #12/6 attach_probe/kprobe-sleepable:OK
> #12/7 attach_probe/uprobe-lib:OK
> #12/8 attach_probe/uprobe-sleepable:OK
> #12/9 attach_probe/uprobe-ref_ctr:OK
> #12 attach_probe:OK
> Summary: 1/9 PASSED, 0 SKIPPED, 0 FAILED
>
> So this must be a config issue.
> I'm not sure what is causing __s390x_sys_nanosleep to be notrace, but this doesn't look normal.
Hi, thank you for taking a look. Do they succeed if you run prior
tests too? I remember situations when a test would succeed when run
independently, but fail when running after other tests.
>
> I also see that the newer test runs are green:
>
> https://github.com/kernel-patches/bpf/actions/runs/14182247375
>
> Do you know if something changed in the meantime?
Yeah, I just disabled the tests failing on s390x for now to unblock
the CI. This is temporary.
A little off-topic: it looks like ebpf runners are offline again,
could be due to recent github runner version bump.
>
> Best regards,
> Ilya
next prev parent reply other threads:[~2025-03-31 22:45 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 [this message]
[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
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=7d55acbf6e6b20f9e8d679883c1e77391e80b304@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--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