From: Eryu Guan <eguan@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2] generic/235: Fix false failures for some quota formats
Date: Thu, 21 Jul 2016 18:45:13 +0800 [thread overview]
Message-ID: <20160721104513.GE27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1469091306-8559-1-git-send-email-jack@suse.cz>
On Thu, Jul 21, 2016 at 10:55:06AM +0200, Jan Kara wrote:
> Different quota format may print additional information in repquota(8)
> output after standard quota information is printed. If format does
> support this additional printouts, repquota(8) will separate possible
> output by two empty lines even if format handler doesn't actually
> printout anything (which is currently always the case for queries test
> generic/235 does). If format doesn't support additional printouts, these
> two empty lines are not present in the output. This inconsistency causes
> false failures for some quota formats.
>
> Fix the problem by filtering out empty lines out of repquota(8) output.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> tests/generic/235 | 9 +++++++--
> tests/generic/235.out | 8 --------
> 2 files changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/tests/generic/235 b/tests/generic/235
> index 59456b67c092..d42054efee91 100755
> --- a/tests/generic/235
> +++ b/tests/generic/235
> @@ -46,6 +46,11 @@ _require_scratch
> _require_quota
> _require_user
>
> +_repquota()
> +{
> + repquota -u -g $SCRATCH_MNT | grep -v -E '^root|^$' | _filter_scratch
> +}
Usually we name local functions without the leading "_", which is for
common helpers from common/rc etc. Do you mind if I rename it to
"do_repquota"?
Thanks,
Eryu
next prev parent reply other threads:[~2016-07-21 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 8:55 [PATCH v2] generic/235: Fix false failures for some quota formats Jan Kara
2016-07-21 10:45 ` Eryu Guan [this message]
2016-07-21 12:21 ` Jan Kara
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=20160721104513.GE27776@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
/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