All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: david@fromorbit.com, fstests@vger.kernel.org, darrick.wong@oracle.com
Subject: Re: [PATCH v2] check: Make the test harness unmount fs when finishing a test
Date: Tue, 22 May 2018 17:57:25 +0800	[thread overview]
Message-ID: <5B03E985.2070501@cn.fujitsu.com> (raw)
In-Reply-To: <1526969013-16134-1-git-send-email-yangx.jy@cn.fujitsu.com>

On 2018/05/22 14:03, Xiao Yang wrote:
> Finishing xfs/132 left a shutdown scratch fs and the test harness didn't
> unmount the fs(because we told it not to check the fs) so the test harness
> called by subsequent xfs/133 tried to "test -d $SCRATCH_MNT" and received
> the IO error from the dead fs.
>
> i.e. Running xfs/132 and xfs/133 together got the following error:
> ------------------------------------------------------------
> ...
> xfs/132 1s ... 1s
> xfs/133 1s ... [failed, exit status 1] - output mismatch (see /var/lib/xfstests/results//xfs/133.out.bad)
> ...
> QA output created by 133
> -Format and mount
> -Corrupt filesystem
> -Remount, try to append
> -Write did not succeed (ok).
> +SCRATCH_DEV=/dev/sda11 is mounted but not on SCRATCH_MNT=common/config: - aborting
> +Already mounted result:
> +/dev/sda11 /mnt/xfstests/scratch
> ...
> ------------------------------------------------------------
>
> Even if we don't check fs, the test harness is supposed to unmount fs and
> return an initial state before running the next test.
>
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
> ---
>  check | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/check b/check
> index 96198ac..a0d5364 100755
> --- a/check
> +++ b/check
> @@ -489,10 +489,14 @@ _check_filesystems()
>  	if [ -f ${RESULT_DIR}/require_test ]; then
>  		_check_test_fs || err=true
>  		rm -f ${RESULT_DIR}/require_test*
> +	else
> +		_test_unmount
>  	fi
>  	if [ -f ${RESULT_DIR}/require_scratch ]; then
>  		_check_scratch_fs || err=true
>  		rm -f ${RESULT_DIR}/require_scratch*
> +	else
> +		_scratch_unmount
Hi,

Sorry, some tests have unmounted them inside, so drop the stderr from
umount.
The v3 patch is coming. :-(

Thanks,
Xiao Yang
>  	fi
>  }
>  




      parent reply	other threads:[~2018-05-22  9:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-19  4:32 [PATCH] xfs/132: umount scratch device after finishing test Xiao Yang
2018-05-21  2:36 ` Dave Chinner
2018-05-21  7:45   ` Xiao Yang
2018-05-21 22:46     ` Dave Chinner
2018-05-22  4:06       ` Xiao Yang
2018-05-22  5:19         ` Dave Chinner
2018-05-22  6:03           ` [PATCH v2] check: Make the test harness unmount fs when finishing a test Xiao Yang
2018-05-22  9:49             ` [PATCH v3] " Xiao Yang
2018-05-22 22:14               ` Dave Chinner
2018-05-22  9:57             ` Xiao Yang [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=5B03E985.2070501@cn.fujitsu.com \
    --to=yangx.jy@cn.fujitsu.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=fstests@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 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.