BPF List
 help / color / mirror / Atom feed
From: Daniel Xu <dlxu@meta.com>
To: Jason Xing <kerneljasonxing@gmail.com>,
	"bot+bpf-ci@kernel.org" <bot+bpf-ci@kernel.org>
Cc: kernel-ci <kernel-ci@meta.com>,
	"andrii@kernel.org" <andrii@kernel.org>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>,
	"martin.lau@linux.dev" <martin.lau@linux.dev>,
	bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH bpf-next v1 0/2] selftests: fix two small compilation errors
Date: Thu, 6 Feb 2025 10:21:54 +0000	[thread overview]
Message-ID: <e937be5a-d0c9-4d80-9835-c5a2be0e6003@meta.com> (raw)
In-Reply-To: <CAL+tcoAUKArVkV_O2nv-D_K8qiRm6W3YkDe8=rUrGbxUxJmqmg@mail.gmail.com>

Hi Jason,

cc bpf@vger

On 2/5/25 11:56 PM, Jason Xing wrote:
> On Thu, Feb 6, 2025 at 5:28 AM <bot+bpf-ci@kernel.org> wrote:
>> Dear patch submitter,
>>
>> CI has tested the following submission:
>> Status:     FAILURE
>> Name:       [bpf-next,v1,0/2] selftests: fix two small compilation errors
>> Patchwork:  https://patchwork.kernel.org/project/netdevbpf/list/?series=930276&state=*
>> Matrix:     https://github.com/kernel-patches/bpf/actions/runs/13165816880
>>
>> Failed jobs:
>> test_progs-aarch64-gcc: https://github.com/kernel-patches/bpf/actions/runs/13165816880/job/36746357575
> I'm afraid this has nothing to do with the series?
> Traceback (most recent call last):
> 5288 File "/tmp/work/_actions/libbpf/ci/v3/run-vmtest/print_test_summary.py",
> line 85, in <module>
> 5289 json_summary = json.load(f)
> 5290 ^^^^^^^^^^^^
> 5291 File "/usr/lib/python3.12/json/__init__.py", line 293, in load
> 5292 return loads(fp.read(),
> 5293 ^^^^^^^^^^^^^^^^
> 5294 File "/usr/lib/python3.12/json/__init__.py", line 346, in loads
> 5295 return _default_decoder.decode(s)
> 5296 ^^^^^^^^^^^^^^^^^^^^^^^^^^
> 5297 File "/usr/lib/python3.12/json/decoder.py", line 337, in decode
> 5298 obj, end = self.raw_decode(s, idx=_w(s, 0).end())
> 5299 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 5300 File "/usr/lib/python3.12/json/decoder.py", line 355, in raw_decode
> 5301 raise JSONDecodeError("Expecting value", s, err.value) from None
> 5302json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
> 5303Error: Process completed with exit code 2
>
> Am I missing something?

If you expand the "test_progs" section right above that, you'll see:

   Caught signal #11!
   Stack trace:
   ./test_progs(crash_handler+0x34)[0xaaaad4e05bfc]
   linux-vdso.so.1(__kernel_rt_sigreturn+0x0)[0xffff85106850]
   ./test_progs(+0x45874)[0xaaaad4a25874]
   ./test_progs(htab_lookup_elem+0x3c)[0xaaaad4a258e4]
   ./test_progs(+0x45b74)[0xaaaad4a25b74]
   ./test_progs(+0x4646c)[0xaaaad4a2646c]
   ./test_progs(test_arena_htab+0x48)[0xaaaad4a264f4]
   ./test_progs(+0x426258)[0xaaaad4e06258]
   ./test_progs(main+0x694)[0xaaaad4e080a0]
   /lib/aarch64-linux-gnu/libc.so.6(+0x284c4)[0xffff84eb84c4]
/lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98)[0xffff84eb8598]
   ./test_progs(_start+0x30)[0xaaaad4a1faf0]
   /tmp/work/_actions/libbpf/ci/v3/run-vmtest/run-bpf-selftests.sh: line 
26:   101 Segmentation fault      ./${selftest} ${args} --json-summary 
"${json_file}"

The infra couldn't parse the stack as json (rightly so).


Thanks,

Daniel



  parent reply	other threads:[~2025-02-06 10:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04  2:39 [PATCH bpf-next v1 0/2] selftests: fix two small compilation errors Jason Xing
2025-02-04  2:39 ` [PATCH bpf-next v1 1/2] bpf: changes_pkt_data: correct the 'main' error Jason Xing
2025-02-07  6:04   ` Martin KaFai Lau
2025-02-07  6:48     ` Jason Xing
2025-02-11 20:06       ` Martin KaFai Lau
2025-02-04  2:39 ` [PATCH bpf-next v1 2/2] bpf: sockopt_sk: fix 'undeclared' definition error Jason Xing
2025-02-05  2:57   ` Hou Tao
2025-02-05  3:27     ` Jason Xing
2025-02-05  9:30       ` Hou Tao
2025-02-05  9:38         ` Jason Xing
2025-02-11 19:40       ` Martin KaFai Lau
     [not found] ` <81c94bf316ea2971f3454e32fdeae4061919458241f6f4c2c80cb0f20d06f144@mail.kernel.org>
     [not found]   ` <CAL+tcoAUKArVkV_O2nv-D_K8qiRm6W3YkDe8=rUrGbxUxJmqmg@mail.gmail.com>
2025-02-06 10:21     ` Daniel Xu [this message]
2025-02-06 12:13       ` [PATCH bpf-next v1 0/2] selftests: fix two small compilation errors Jason Xing
2025-02-11  7:52 ` Jason Xing

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=e937be5a-d0c9-4d80-9835-c5a2be0e6003@meta.com \
    --to=dlxu@meta.com \
    --cc=andrii@kernel.org \
    --cc=bot+bpf-ci@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-ci@meta.com \
    --cc=kerneljasonxing@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox