netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Allison Henderson <allison.henderson@oracle.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "rds-devel@oss.oracle.com" <rds-devel@oss.oracle.com>,
	Vegard Nossum <vegard.nossum@oracle.com>,
	"oberpar@linux.ibm.com" <oberpar@linux.ibm.com>,
	Chuck Lever III <chuck.lever@oracle.com>
Subject: Re: [RFC net-next 0/3] selftests: rds selftest
Date: Sun, 9 Jun 2024 18:08:12 +0000	[thread overview]
Message-ID: <c03b8bf87f6a1a1c19647832db0e3fa294eec773.camel@oracle.com> (raw)
In-Reply-To: <20240607003631.32484-1-allison.henderson@oracle.com>

On Thu, 2024-06-06 at 17:36 -0700, allison.henderson@oracle.com wrote:
+cc Chuck Lever, Peter Oberparleiter, Vegard Nossum, rds-devel

> From: Allison Henderson <allison.henderson@oracle.com>
> 
> Hi All,
> 
> This series is a new selftest that Vegard, Chuck and myself have been
> working on to provide some test coverage for rds.  It still has a few
> bugs to work out, so it's not quite ready for submission yet.  But we
> thought an RFC would be a good idea just to collect some feed back to
> see what people think.  Some things to be aware of that we are still
> working through:
> 
>   Occasionally we see intermittent hangs during the send and recv.
>   So we still need to track down and address the cause
> 
>   We may still add a time out to handle unexpected hangs
> 
>   We've been having some trouble getting gcov to generate a report if
>   the version of gcov doesn't match the version of gcc installed.  So
>   we may further adapt the test to omit the coverage report if the
>   required dependencies are not met
> 
>   Some distros are still not collecting meaningfull gcda data and
>   generate an empty report, so we are still trying to figure out the
>   cause of that
> 
>   May still add more exit codes for PASS/FAIL/BROKEN/CONFIG
> conditions
> 
> Questions and comments appreciated.  Thanks everyone!
> 
> Allison
> 
> Vegard Nossum (3):
>   .gitignore: add .gcda files
>   net: rds: add option for GCOV profiling
>   selftests: rds: add testing infrastructure
> 
>  .gitignore                                 |   1 +
>  MAINTAINERS                                |   1 +
>  net/rds/Kconfig                            |   9 +
>  net/rds/Makefile                           |   5 +
>  tools/testing/selftests/Makefile           |   1 +
>  tools/testing/selftests/net/rds/Makefile   |  13 ++
>  tools/testing/selftests/net/rds/README.txt |  15 ++
>  tools/testing/selftests/net/rds/config.sh  |  33 +++
>  tools/testing/selftests/net/rds/init.sh    |  49 +++++
>  tools/testing/selftests/net/rds/run.sh     | 168 ++++++++++++++
>  tools/testing/selftests/net/rds/test.py    | 244
> +++++++++++++++++++++
>  11 files changed, 539 insertions(+)
>  create mode 100644 tools/testing/selftests/net/rds/Makefile
>  create mode 100644 tools/testing/selftests/net/rds/README.txt
>  create mode 100755 tools/testing/selftests/net/rds/config.sh
>  create mode 100755 tools/testing/selftests/net/rds/init.sh
>  create mode 100755 tools/testing/selftests/net/rds/run.sh
>  create mode 100644 tools/testing/selftests/net/rds/test.py
> 


      parent reply	other threads:[~2024-06-09 18:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  0:36 [RFC net-next 0/3] selftests: rds selftest allison.henderson
2024-06-07  0:36 ` [RFC net-next 1/3] .gitignore: add .gcda files allison.henderson
2024-06-09 18:08   ` Allison Henderson
2024-06-07  0:36 ` [RFC net-next 2/3] net: rds: add option for GCOV profiling allison.henderson
2024-06-09 18:08   ` Allison Henderson
2024-06-07  0:36 ` [RFC net-next 3/3] selftests: rds: add testing infrastructure allison.henderson
2024-06-07 20:24   ` Simon Horman
2024-06-09 18:08     ` Allison Henderson
2024-06-09 18:08 ` Allison Henderson [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=c03b8bf87f6a1a1c19647832db0e3fa294eec773.camel@oracle.com \
    --to=allison.henderson@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=netdev@vger.kernel.org \
    --cc=oberpar@linux.ibm.com \
    --cc=rds-devel@oss.oracle.com \
    --cc=vegard.nossum@oracle.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;
as well as URLs for NNTP newsgroup(s).