From: patchwork-bot+netdevbpf@kernel.org
To: Roxana Nicolescu <roxana.nicolescu@canonical.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, shuah@kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] selftest: fib_tests: Always cleanup before exit
Date: Tue, 21 Feb 2023 11:20:18 +0000 [thread overview]
Message-ID: <167697841800.23862.3511124706194686998.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230220110400.26737-1-roxana.nicolescu@canonical.com>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 20 Feb 2023 12:03:59 +0100 you wrote:
> Usually when a subtest is executed, setup and cleanup functions
> are linearly called at the beginning and end of it.
> In some of them, `set -e` is used before executing commands.
> If one of the commands returns a non zero code, the whole script exists
> without cleaning up the resources allocated at setup.
> This can affect the next tests that use the same resources,
> leading to a chain of failures.
>
> [...]
Here is the summary with links:
- [1/1] selftest: fib_tests: Always cleanup before exit
https://git.kernel.org/netdev/net/c/b60417a9f2b8
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:[~2023-02-21 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 11:03 [PATCH 0/1] selftest: fib_tests: Always cleanup before exit Roxana Nicolescu
2023-02-20 11:04 ` [PATCH 1/1] " Roxana Nicolescu
2023-02-21 11:20 ` 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=167697841800.23862.3511124706194686998.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roxana.nicolescu@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox