[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240311091751.5c4f2947@kernel.org>
Date: Mon, 11 Mar 2024 09:17:51 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Mirsad Todorovac <mirsad.todorovac@....unizg.hr>
Cc: netdev@...r.kernel.org, Guillaume Nault <gnault@...hat.com>, "David S.
Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, Shuah Khan <shuah@...nel.org>,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org, David Ahern
<dsahern@...il.com>
Subject: Re: [BUG net-next] fcnal-test.sh: 4 (four) tests FAIL
On Sat, 9 Mar 2024 19:45:15 +0100 Mirsad Todorovac wrote:
> In the vanilla net-next tree build of v6.8-rc7-2348-g75c2946db360, with up-to-date
> iproute2 built tools, fcnal-test.sh reports certain failures:
>
> --------------------------------------------------------------------------------------
> # TEST: ping local, VRF bind - VRF IP [FAIL]
> # TEST: ping local, device bind - ns-A IP [FAIL]
> # TEST: ping local, VRF bind - VRF IP [FAIL]
> # TEST: ping local, device bind - ns-A IP [FAIL]
> --------------------------------------------------------------------------------------
Adding David A to CC.
It rings a bell. We also build ping from source when running the tests
locally, I have in my notes "AWS iputils are buggy, use iputils.git"
but unfortunately I didn't make a note which tests were failing without
it. David might remember..
Powered by blists - more mailing lists