From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fs-test.sh: minor fixes
Date: Wed, 12 Aug 2015 09:09:13 -0600 [thread overview]
Message-ID: <55CB6199.6040005@wwwdotorg.org> (raw)
In-Reply-To: <CANoR_OBOfnTQOQFUoEfVHG=1FYV4xb5-yaX_nOQTF=q8bBsbUQ@mail.gmail.com>
On 08/12/2015 08:29 AM, Suriyan Ramasami wrote:
> Hi Stephen,
>
> Small nitpick, just to be consistent (for that particular line), we
> could use OUT_FILE="${OUT}.${1}.${fs}.out"
I thought about that, but that would be inconsistent with plain $1 being
used everywhere else:-) Which option do you prefer?
> Acked-by: Suriyan Ramasami <suriyan.r@gmail.com
> <mailto:suriyan.r@gmail.com>>
>
> Best Regards
>
> On Mon, Aug 10, 2015 at 9:45 PM, Stephen Warren <swarren@wwwdotorg.org
> <mailto:swarren@wwwdotorg.org>> wrote:
>
> - Re-direct stderr into the log files, so any errors U-Boot emits are
> visible in the logs. This is relevant if the "reset" shell command
> attempts to report that it's not supported on the sandbox board.
> - Fix test_fs_nonfs() to name the files it created differently for each
> invocation. Otherwise, the logs from different tests overwrite
> each-other.
>
> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org
> <mailto:swarren@wwwdotorg.org>>
> ---
> test/fs/fs-test.sh | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/test/fs/fs-test.sh b/test/fs/fs-test.sh
> index a4fb0559625d..b88a67ca066d 100755
> --- a/test/fs/fs-test.sh
> +++ b/test/fs/fs-test.sh
> @@ -485,9 +485,9 @@ function test_fs_nonfs() {
> echo "Creating files in $fs image if not already present."
> create_files $IMAGE $MD5_FILE_FS
>
> - OUT_FILE="${OUT}.fs.${fs}.out"
> + OUT_FILE="${OUT}.$1.${fs}.out"
> test_image $IMAGE $fs $SMALL_FILE $BIG_FILE $1 "" \
> - > ${OUT_FILE}
> + > ${OUT_FILE} 2>&1
> check_results $OUT_FILE $MD5_FILE_FS $SMALL_FILE $BIG_FILE \
> $WRITE_FILE
> TOTAL_FAIL=$((TOTAL_FAIL + FAIL))
> @@ -535,7 +535,7 @@ for fs in ext4 fat; do
>
> OUT_FILE="${OUT}.sb.${fs}.out"
> test_image $IMAGE $fs $SMALL_FILE $BIG_FILE sb
> `pwd`/$MOUNT_DIR \
> - > ${OUT_FILE}
> + > ${OUT_FILE} 2>&1
> sudo umount "$MOUNT_DIR"
> rmdir "$MOUNT_DIR"
>
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2015-08-12 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 4:45 [U-Boot] [PATCH] fs-test.sh: minor fixes Stephen Warren
2015-08-12 14:29 ` Suriyan Ramasami
2015-08-12 15:09 ` Stephen Warren [this message]
2015-08-12 17:48 ` Suriyan Ramasami
2015-08-18 17:52 ` [U-Boot] " Tom Rini
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=55CB6199.6040005@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.