Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kbingham@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org, Kieran Bingham <kieran@bingham.xyz>
Subject: Re: [PATCH 1/5] scripts: Test suite runner
Date: Fri, 25 Nov 2016 20:21:20 +0200	[thread overview]
Message-ID: <8987945.smZSHVWX73@avalon> (raw)
In-Reply-To: <1480082356-23380-2-git-send-email-kbingham@kernel.org>

Hi Kieran,

Thank you for the patch.

On Friday 25 Nov 2016 13:59:12 Kieran Bingham wrote:
> From: Kieran Bingham <kieran@bingham.xyz>
> 
> Provide a utility script to execute all vsp unit tests, as well
> as the option to execute multiple iterations of the suite.
> 
> Signed-off-by: Kieran Bingham <kieran@bingham.xyz>
> ---
>  scripts/vsp-tests.sh | 46 ++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 46 insertions(+)
>  create mode 100755 scripts/vsp-tests.sh
> 
> diff --git a/scripts/vsp-tests.sh b/scripts/vsp-tests.sh
> new file mode 100755
> index 000000000000..e5ffa0ec4236
> --- /dev/null
> +++ b/scripts/vsp-tests.sh
> @@ -0,0 +1,46 @@
> +#!/bin/sh
> +
> +##
> +## VSP Tests runner
> +##
> +## Automatically execute all vsp-unit tests
> +## Move test failure results to a specific folder for
> +## the running kernel version
> +##
> +## An argument can be provided to specify the number of
> +## iterations to perform
> +##
> +## usage:
> +##  ./vsp-tests.sh <n>
> +##
> +##   n: Number of iterations to execute test suite
> +##
> +
> +KERNEL_VERSION=`uname -r`
> +
> +run_test() {
> +	echo $1
> +	./$1
> +
> +	if [ $(ls *.bin 2>/dev/null | wc -l) != 0 ];
> +	then
> +		RESULTS_DIR=$KERNEL_VERSION/test-$1/$2/
> +
> +		echo "Moving *.bin to test-$1/$2/";

You can remove the ; at the end of the lines.

> +		mkdir -p $RESULTS_DIR;
> +		echo "mv *.bin $RESULTS_DIR";

Do we really need this message ?

> +		mv *.bin $RESULTS_DIR;
> +	fi;
> +}
> +
> +run_suite() {
> +	echo "Test loop $1"
> +
> +	for test in vsp-unit-test*.sh; do
> +		run_test $test $1;
> +	done;
> +}
> +
> +for loop in `seq 1 1 $1`; do
> +	run_suite $loop
> +done;

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2016-11-25 18:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 13:59 [PATCH 0/5] VSP-Tests: Add suspend resume tests and helpers Kieran Bingham
2016-11-25 13:59 ` [PATCH 1/5] scripts: Test suite runner Kieran Bingham
2016-11-25 18:21   ` Laurent Pinchart [this message]
2016-11-25 18:47     ` Kieran Bingham
2016-11-25 13:59 ` [PATCH 2/5] scripts: Provide bin2png.sh helper Kieran Bingham
2016-11-25 17:55   ` Laurent Pinchart
2016-11-25 18:04     ` Kieran Bingham
2016-11-25 13:59 ` [PATCH 3/5] logger: Log to the FTrace buffer if tracing is enabled Kieran Bingham
2016-11-25 17:40   ` Laurent Pinchart
2016-11-25 18:10     ` Kieran Bingham
2016-11-25 18:27       ` Laurent Pinchart
2016-11-25 13:59 ` [PATCH 4/5] tests: Test suspend/resume on idle pipelines Kieran Bingham
2016-11-25 17:13   ` Laurent Pinchart
2016-11-25 18:14     ` Kieran Bingham
2016-11-25 13:59 ` [PATCH 5/5] tests: Test suspend/resume on active pipelines Kieran Bingham
2016-11-25 17:10   ` Laurent Pinchart
2016-11-25 18:40     ` Kieran Bingham
2016-11-25 19:03       ` Laurent Pinchart

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=8987945.smZSHVWX73@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=kbingham@kernel.org \
    --cc=kieran@bingham.xyz \
    --cc=linux-renesas-soc@vger.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