From: Eric Whitney <enwlinux@gmail.com>
To: Eric Whitney <enwlinux@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: don't remove trailing zeros from integers
Date: Fri, 1 Mar 2013 12:36:59 -0500 [thread overview]
Message-ID: <20130301173658.GB6449@wallace> (raw)
In-Reply-To: <20130301041344.GA3206@rocky>
* Eric Whitney <enwlinux@gmail.com>:
> * Eric Sandeen <sandeen@redhat.com>:
> > On 2/28/13 6:26 PM, Eric Whitney wrote:
> > > _within_tolerance strips trailing zeros from the min and max range
> > > values it outputs. This leads to damage if the min or max value is
> > > an integer containing trailing zeros rather than a real number with
> > > a fractional part containing trailing zeros. Xfstest 289 can exhibit
> > > this problem when its input is out of range. Modify the code so it
> > > will only remove trailing zeros found after a decimal point.
> >
> > whoops, that's not too good.
> >
> > It's only for the output message in a failure case though, correct?
> > But it makes the error output unhelpful.
>
> Right on both counts. We'd noticed the error output was confusing a few
> months ago when you fixed an ext4 free space reporting problem (this is an
> IOU) - 1280000 reported as 128 in that case.
>
> >
> > Seems a little weird that it still leaves the trailing decimal:
> >
> > $ echo 20000.00 | sed -e '/\./s/0*$//'
> > 20000.
> >
> > but that's not a big deal. The patch makes it better and
> > the output is understandable even if it has a trailing
> > decimal (which it had before anyway) so:
> >
> > Reviewed-by: Eric Sandeen <sandeen@redhat.com>
>
> I'd reached the same conclusion, but if preferred I'll take this farther
> and eliminate the trailing decimal.
>
On further consideration, it's easy enough to clean up the trailing decimal
and it's just better that way, even for an error case. There's at least one
fix that isn't elegant but works. I'll send along a V2 shortly.
Regards,
Eric
> Thanks for the review!
>
> Eric
>
> >
> > > Signed-off-by: Eric Whitney <enwlinux@gmail.com>
> > > ---
> > > common.filter | 6 ++++--
> > > 1 file changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/common.filter b/common.filter
> > > index 9e4c90c..1df2f97 100644
> > > --- a/common.filter
> > > +++ b/common.filter
> > > @@ -106,8 +106,10 @@ EOF
> > >
> > > # fix up min, max precision for output
> > > # can vary for 5.3, 6.2
> > > - _min=`echo $_min | sed -e 's/0*$//'` # get rid of trailling zeroes
> > > - _max=`echo $_max | sed -e 's/0*$//'` # get rid of trailling zeroes
> > > +
> > > + # remove any trailing zeroes from min, max if they have fractional parts
> > > + _min=`echo $_min | sed -e '/\./s/0*$//'`
> > > + _max=`echo $_max | sed -e '/\./s/0*$//'`
> > >
> > > if [ $_in_range -eq 1 ]
> > > then
> > >
> >
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-03-01 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 0:26 [PATCH] xfstests: don't remove trailing zeros from integers Eric Whitney
2013-03-01 3:03 ` Eric Sandeen
2013-03-01 4:13 ` Eric Whitney
2013-03-01 17:36 ` Eric Whitney [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=20130301173658.GB6449@wallace \
--to=enwlinux@gmail.com \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.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