From: Varun R Mallya <varunrmallya@gmail.com>
To: andrii@kernel.org, eddyz87@gmail.com, toke@redhat.com
Cc: ast@kernel.org, daniel@iogearbox.net, song@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix const qualifier warning in fexit_bpf2bpf.c
Date: Fri, 6 Mar 2026 17:41:12 +0530 [thread overview]
Message-ID: <aarEYMXNzVhvNNMs@computer> (raw)
In-Reply-To: <20260305222132.470700-1-varunrmallya@gmail.com>
Looks like the CI failed on this:
> CI has tested the following submission:
> Status: FAILURE
> Name: [bpf-next] selftests/bpf: Fix const qualifier warning in fexit_bpf2bpf.c
> Patchwork: https://patchwork.kernel.org/project/netdevbpf/list/?series=1062212&state=*
> Matrix: https://github.com/kernel-patches/bpf/actions/runs/22741682920
>
> Failed jobs:
> test_progs_parallel-x86_64-gcc-15: https://github.com/kernel-patches/bpf/actions/runs/22741682920/job/65957069283
>
>
The CI Failure seems to be unrelated, though:
```
With the provided path, there will be 109 files uploaded
Artifact name is valid!
Root directory input is valid!
Error: The path for one of the files in artifact is not valid:
/packets-135-10-net_timestamping__INET4:_bpf_timestamping-net_timestamping_ns.log.
Contains the following character: Colon :
Invalid characters include: Double quote ", Colon :, Less than <, Greater than >,
Vertical bar |, Asterisk *, Question mark ?, Carriage return \r, Line feed \n
The following characters are not allowed in files that are uploaded due to
limitations with certain file systems such as NTFS. To maintain file system
agnostic behavior, these characters are intentionally not allowed to prevent
potential problems with downloads on different file systems.
```
The selftests did pass.
next prev parent reply other threads:[~2026-03-06 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 22:21 [PATCH bpf-next] selftests/bpf: Fix const qualifier warning in fexit_bpf2bpf.c Varun R Mallya
2026-03-06 1:16 ` Menglong Dong
2026-03-06 1:40 ` Alexei Starovoitov
2026-03-06 2:26 ` Alexei Starovoitov
2026-03-06 2:47 ` Menglong Dong
2026-03-06 12:11 ` Varun R Mallya [this message]
2026-03-11 18:20 ` patchwork-bot+netdevbpf
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=aarEYMXNzVhvNNMs@computer \
--to=varunrmallya@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=song@kernel.org \
--cc=toke@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