public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
	netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	shuah@kernel.org, jbacik@fb.com, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net] selftests: reuseaddr_conflict: add missing new line at the end of the output
Date: Sat, 30 Mar 2024 00:35:51 +0500	[thread overview]
Message-ID: <489b5f4c-a7a0-4c8a-888f-ccf09d4bd81f@collabora.com> (raw)
In-Reply-To: <20240329160559.249476-1-kuba@kernel.org>

On 3/29/24 9:05 PM, Jakub Kicinski wrote:
> The netdev CI runs in a VM and captures serial, so stdout and
> stderr get combined. Because there's a missing new line in
> stderr the test ends up corrupting KTAP:
> 
>   # Successok 1 selftests: net: reuseaddr_conflict
> 
> which should have been:
> 
>   # Success
>   ok 1 selftests: net: reuseaddr_conflict
> 
> Fixes: 422d8dc6fd3a ("selftest: add a reuseaddr test")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Muhammad Usama Anjum <usama.anjum@collabora.com>

> ---
> Low risk and seems worth backporting to stable, hence the fixes tag.
Agreed to back port it as ok or not ok must appear at the start of the line
to indicate the status of the test.

> 
> CC: shuah@kernel.org
> CC: jbacik@fb.com
> CC: linux-kselftest@vger.kernel.org
> ---
>  tools/testing/selftests/net/reuseaddr_conflict.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/net/reuseaddr_conflict.c b/tools/testing/selftests/net/reuseaddr_conflict.c
> index 7c5b12664b03..bfb07dc49518 100644
> --- a/tools/testing/selftests/net/reuseaddr_conflict.c
> +++ b/tools/testing/selftests/net/reuseaddr_conflict.c
> @@ -109,6 +109,6 @@ int main(void)
>  	fd1 = open_port(0, 1);
>  	if (fd1 >= 0)
>  		error(1, 0, "Was allowed to create an ipv4 reuseport on an already bound non-reuseport socket with no ipv6");
> -	fprintf(stderr, "Success");
> +	fprintf(stderr, "Success\n");
>  	return 0;
>  }

-- 
BR,
Muhammad Usama Anjum

  reply	other threads:[~2024-03-29 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 16:05 [PATCH net] selftests: reuseaddr_conflict: add missing new line at the end of the output Jakub Kicinski
2024-03-29 19:35 ` Muhammad Usama Anjum [this message]
2024-04-02  4:20 ` patchwork-bot+netdevbpf

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=489b5f4c-a7a0-4c8a-888f-ccf09d4bd81f@collabora.com \
    --to=usama.anjum@collabora.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jbacik@fb.com \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox