From: Jakub Kicinski <kuba@kernel.org>
To: thinker.li@gmail.com
Cc: netdev@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
kernel-team@meta.com, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, pabeni@redhat.com, liuhangbin@gmail.com,
sinquersw@gmail.com, kuifeng@meta.com
Subject: Re: [PATCH net-next 5/5] selftests/net: Adding test cases of replacing routes and route advertisements.
Date: Wed, 31 Jan 2024 11:20:49 -0800 [thread overview]
Message-ID: <20240131112049.2402e164@kernel.org> (raw)
In-Reply-To: <20240131064041.3445212-6-thinker.li@gmail.com>
On Tue, 30 Jan 2024 22:40:41 -0800 thinker.li@gmail.com wrote:
> + N_PERM=$($IP -6 route list |grep -v expires|grep 2001:20::|wc -l)
> + if [ $N_PERM -ne 100 ]; then
> + echo "FAIL: expected 100 permanent routes, got $N_PERM"
> + ret=1
> + else
> + ret=0
> + fi
This fails on our slow VM:
# TEST: expected 100 routes with expires, got 98 [FAIL]
on a VM with kernel debug enable the test times out (it doesn't print
anything for 10min):
https://netdev-3.bots.linux.dev/vmksft-net-dbg/results/445222/6-fib-tests-sh/stdout
--
pw-bot: cr
next prev parent reply other threads:[~2024-01-31 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 6:40 [PATCH net-next 0/5] Remove expired routes with a separated list of routes thinker.li
2024-01-31 6:40 ` [PATCH net-next 1/5] net/ipv6: set expires in rt6_add_dflt_router() thinker.li
2024-01-31 6:40 ` [PATCH net-next 2/5] net/ipv6: Remove unnecessary clean thinker.li
2024-01-31 8:29 ` Hangbin Liu
2024-01-31 6:40 ` [PATCH net-next 3/5] net/ipv6: Remove expired routes with a separated list of routes thinker.li
2024-01-31 6:40 ` [PATCH net-next 4/5] net/ipv6: set expires in modify_prefix_route() if RTF_EXPIRES is set thinker.li
2024-01-31 6:40 ` [PATCH net-next 5/5] selftests/net: Adding test cases of replacing routes and route advertisements thinker.li
2024-01-31 19:20 ` Jakub Kicinski [this message]
2024-01-31 21:14 ` Kui-Feng Lee
2024-02-01 8:46 ` Hangbin Liu
2024-02-01 17:14 ` Kui-Feng Lee
2024-02-02 2:25 ` Hangbin Liu
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=20240131112049.2402e164@kernel.org \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=liuhangbin@gmail.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sinquersw@gmail.com \
--cc=thinker.li@gmail.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 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.