From: Byeonguk Jeong <jungbu2855@gmail.com>
To: Hou Tao <houtao1@huawei.com>
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
Alexei Starovoitov <ast@kernel.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf] selftests/bpf: Add a copyright notice to lpm_trie_map_get_next_key
Date: Sun, 3 Nov 2024 06:04:15 +0000 [thread overview]
Message-ID: <ZycSXwjH4UTvx-Cn@ub22> (raw)
In-Reply-To: <Zyb6cVpIqmMBld4U@ub22>
Hi,
The selftest "verifier_bits_iter/bad words" has been failed with
retval 115, while I did not touched anything but a comment.
Do you have any idea why it failed? I am not sure whether it indicates
any bugs in the kernel.
Best,
Byeonguk
On Sun, Nov 03, 2024 at 04:41:26AM +0000, bot+bpf-ci@kernel.org wrote:
> Dear patch submitter,
>
> CI has tested the following submission:
> Status: FAILURE
> Name: [bpf] selftests/bpf: Add a copyright notice to lpm_trie_map_get_next_key
> Patchwork: https://patchwork.kernel.org/project/netdevbpf/list/?series=905730&state=*
> Matrix: https://github.com/kernel-patches/bpf/actions/runs/11648453401
>
> Failed jobs:
> test_progs_no_alu32-s390x-gcc: https://github.com/kernel-patches/bpf/actions/runs/11648453401/job/32434970670
>
> First test_progs failure (test_progs_no_alu32-s390x-gcc):
> #433 verifier_bits_iter
> tester_init:PASS:tester_log_buf 0 nsec
> process_subtest:PASS:obj_open_mem 0 nsec
> process_subtest:PASS:specs_alloc 0 nsec
> #433/13 verifier_bits_iter/bad words
> run_subtest:PASS:obj_open_mem 0 nsec
> run_subtest:PASS:unexpected_load_failure 0 nsec
> do_prog_test_run:PASS:bpf_prog_test_run 0 nsec
> run_subtest:FAIL:1035 Unexpected retval: 115 != 0
>
>
> Please note: this email is coming from an unmonitored mailbox. If you have
> questions or feedback, please reach out to the Meta Kernel CI team at
> kernel-ci@meta.com.
next prev parent reply other threads:[~2024-11-03 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 4:22 [PATCH bpf] selftests/bpf: Add a copyright notice to lpm_trie_map_get_next_key Byeonguk Jeong
2024-11-03 6:04 ` Byeonguk Jeong [this message]
2024-11-04 1:34 ` Hou Tao
2024-11-04 2:02 ` Byeonguk Jeong
2024-11-05 2:39 ` Hou Tao
2024-11-04 10:07 ` Ilya Leoshkevich
2024-11-05 2:34 ` Hou Tao
2024-11-05 6:21 ` Hou Tao
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=ZycSXwjH4UTvx-Cn@ub22 \
--to=jungbu2855@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=houtao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.