From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
ast@kernel.org, andrii@kernel.org, martin.lau@linux.dev,
netdev@vger.kernel.org, bpf@vger.kernel.org, chantra@meta.com
Subject: Re: pull-request: bpf 2024-07-25
Date: Thu, 25 Jul 2024 07:16:00 -0700 [thread overview]
Message-ID: <20240725071600.2b9c0f62@kernel.org> (raw)
In-Reply-To: <ce07f53f-bbe3-77d1-df59-ab5ce9e750d2@iogearbox.net>
On Thu, 25 Jul 2024 16:13:00 +0200 Daniel Borkmann wrote:
> On 7/25/24 3:30 PM, Jakub Kicinski wrote:
> > On Thu, 25 Jul 2024 13:43:12 +0200 Daniel Borkmann wrote:
> >> Hi David, hi Jakub, hi Paolo, hi Eric,
> >
> > While I have you, is this a known in BPF CI problem?
> >
> > ar: libLLVM.so.19.0: cannot open shared object file: No such file or directory
> >
> > Looks like our BPF CI builds are failing since 8pm PST yesterday.
>
> Looks like you may be one step ahead.. BPF CI runs tests with LLVM17 + LLVM18
> at this point, so we haven't seen that issue yet. Maybe Manu has?
FWIW we got a PR on the list last night which was based on fairly
recent version of Linus's tree. I dropped it from the test queue,
but I suspect once we FF this will come back.
next prev parent reply other threads:[~2024-07-25 14:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 11:43 pull-request: bpf 2024-07-25 Daniel Borkmann
2024-07-25 13:30 ` Jakub Kicinski
2024-07-25 14:13 ` Daniel Borkmann
2024-07-25 14:16 ` Jakub Kicinski [this message]
2024-07-25 18:30 ` Manu Bretelle
2024-07-25 18:40 ` Jakub Kicinski
2024-07-25 19:47 ` Manu Bretelle
2024-07-25 14:50 ` 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=20240725071600.2b9c0f62@kernel.org \
--to=kuba@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chantra@meta.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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;
as well as URLs for NNTP newsgroup(s).