From: Jakub Kicinski <kuba@kernel.org>
To: Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: netdev@vger.kernel.org, Guillaume Nault <gnault@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
David Ahern <dsahern@gmail.com>
Subject: Re: [BUG net-next] fcnal-test.sh: 4 (four) tests FAIL
Date: Mon, 11 Mar 2024 09:17:51 -0700 [thread overview]
Message-ID: <20240311091751.5c4f2947@kernel.org> (raw)
In-Reply-To: <9f24a9c3-4813-4518-9cc4-3923c11981cd@alu.unizg.hr>
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..
next prev parent reply other threads:[~2024-03-11 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 18:45 [BUG net-next] fcnal-test.sh: 4 (four) tests FAIL Mirsad Todorovac
2024-03-11 16:17 ` Jakub Kicinski [this message]
2024-03-11 16:26 ` David Ahern
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=20240311091751.5c4f2947@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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.