Re: s390x: selftests/bpf are failing on CI

["Ihor Solodrai" <ihor.solodrai@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