From: patchwork-bot+netdevbpf@kernel.org
To: Li Zhijian <lizhijian@fujitsu.com>
Cc: davem@davemloft.net, kuba@kernel.org, shuah@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, zhoujie2011@fujitsu.com
Subject: Re: [PATCH] kselftests/net: adapt the timeout to the largest runtime
Date: Thu, 13 Jan 2022 13:00:11 +0000 [thread overview]
Message-ID: <164207881178.26897.5058098241493061619.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220113072859.3431-1-lizhijian@fujitsu.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 13 Jan 2022 15:28:59 +0800 you wrote:
> timeout in settings is used by each case under the same directory, so
> it should adapt to the maximum runtime.
>
> A normally running net/fib_nexthops.sh may be killed by this unsuitable
> timeout. Furthermore, since the defect[1] of kselftests framework,
> net/fib_nexthops.sh which might take at least (300 * 4) seconds would
> block the whole kselftests framework previously.
> $ git grep -w 'sleep 300' tools/testing/selftests/net
> tools/testing/selftests/net/fib_nexthops.sh: sleep 300
> tools/testing/selftests/net/fib_nexthops.sh: sleep 300
> tools/testing/selftests/net/fib_nexthops.sh: sleep 300
> tools/testing/selftests/net/fib_nexthops.sh: sleep 300
>
> [...]
Here is the summary with links:
- kselftests/net: adapt the timeout to the largest runtime
https://git.kernel.org/netdev/net/c/de0e444706ed
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-13 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 7:28 Li Zhijian
2022-01-13 13:00 ` patchwork-bot+netdevbpf [this message]
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=164207881178.26897.5058098241493061619.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=zhoujie2011@fujitsu.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
Powered by JetHome