From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: James Bottomley <JBottomley@Odin.com>,
lkp@01.org, kernel test robot <ying.huang@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [lkp] [string_helpers] 26cfdc920f: kmsg.test_string_helpers:string_get_size(size=#,blk_size=#,units=
Date: Thu, 14 Jan 2016 10:17:48 +0100 [thread overview]
Message-ID: <87lh7s4j0j.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <87d1t4x48h.fsf@yhuang-dev.intel.com> (kernel test robot's message of "Thu, 14 Jan 2016 10:51:58 +0800")
kernel test robot <ying.huang@linux.intel.com> writes:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 26cfdc920f1bb5766ff1493712a4f5a97ee5e484 ("string_helpers: fix precision loss for some inputs")
>
> [ 1.775834] test_string_helpers: Running tests...
> [ 1.775834] test_string_helpers: Running tests...
> [ 1.776987] test_string_helpers: Test 'test_string_get_size_one' failed!
> [ 1.776987] test_string_helpers: Test 'test_string_get_size_one' failed!
> [ 1.778265] test_string_helpers: string_get_size(size = 8192, blk_size = 4096, units = 0
> [ 1.778265] test_string_helpers: string_get_size(size = 8192, blk_size = 4096, units = 0
> [ 1.779732] test_string_helpers: expected: '32.7 MB', got '33.6 MB'
> [ 1.779732] test_string_helpers: expected: '32.7 MB', got '33.6 MB'
Yes, there was a patch updating tests in my series but apparently James's
solution got merged without it. I'll dig it out and send.
--
Vitaly
prev parent reply other threads:[~2016-01-14 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 2:51 [lkp] [string_helpers] 26cfdc920f: kmsg.test_string_helpers:string_get_size(size=#,blk_size=#,units= kernel test robot
2016-01-14 9:17 ` Vitaly Kuznetsov [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=87lh7s4j0j.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=JBottomley@Odin.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=sfr@canb.auug.org.au \
--cc=ying.huang@linux.intel.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