[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240725114040.26c1f483@kernel.org>
Date: Thu, 25 Jul 2024 11:40:40 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Manu Bretelle <chantra@...a.com>
Cc: Daniel Borkmann <daniel@...earbox.net>, "davem@...emloft.net"
<davem@...emloft.net>, "pabeni@...hat.com" <pabeni@...hat.com>,
"edumazet@...gle.com" <edumazet@...gle.com>, Alexei Starovoitov
<ast@...nel.org>, Andrii Nakryiko <andrii@...nel.org>, Martin KaFai Lau
<martin.lau@...ux.dev>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>
Subject: Re: pull-request: bpf 2024-07-25
On Thu, 25 Jul 2024 18:30:22 +0000 Manu Bretelle wrote:
> I did not play with llvm19 yet.
>
> Checking the BPF CI netdev builds that went red yesterday 8pm PST leads to
> https://github.com/kernel-patches/bpf/actions/runs/10087416772
>
> BPF selftests build is failing with:
>
> CC bench_local_storage_create.o
> 3298 CC bench_htab_mem.o
> 3299 CC bench_bpf_crypto.o
> 3300 BINARY xskxceiver
> 3301 <command-line>: error: "_GNU_SOURCE" redefined [-Werror]
> 3302 <command-line>: note: this is the location of the previous definition
> 3303 BINARY xdp_hw_metadata
> 3304 BINARY xdp_features
> 3305 TEST-OBJ [test_maps] htab_map_batch_ops.test.o
> 3306 TEST-OBJ [test_maps] lpm_trie_map_batch_ops.test.o
> 3307 TEST-OBJ [test_maps] sk_storage_map.test.o
> 3308 TEST-OBJ [test_maps] map_percpu_stats.test.o
>
> across all combos or architectures/compilers. I did not see anything related to LLVM19 though.
>
> last failing build was today 5:17 am PST https://github.com/kernel-patches/bpf/actions/runs/10093925751
> with the same symptoms.
>
> First successful at 8:02am: https://github.com/kernel-patches/bpf/actions/runs/10096557745
Ugh, seems like the GitHub UI messes up Firefox's ability to search :(
I see it now, and it makes sense. Linus ended up with cc937dad85aea
which was supposed to never make it upstream.
On the LLVM19 I see this in all outputs:
ar: libLLVM.so.19.0: cannot open shared object file: No such file or directory
But presumably that's harmless, then.
Powered by blists - more mailing lists