From: Loic Dachary <loic@dachary.org>
To: "Miyamae, Takeshi" <miyamae.takeshi@jp.fujitsu.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
"Shiozawa, Kensuke" <shiozawa.kennsu@jp.fujitsu.com>,
"Nakao, Takanori" <nakao.takanori@jp.fujitsu.com>
Subject: Re: SHEC updates to the erasure code non regression corpus
Date: Thu, 12 Feb 2015 10:21:42 +0100 [thread overview]
Message-ID: <54DC70A6.5040108@dachary.org> (raw)
In-Reply-To: <54DC6ED7.8020900@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]
Please ignore this mail, I confused the two threads and you already answered with https://github.com/ceph/ceph/pull/3716. Great :-)
On 12/02/2015 10:13, Loic Dachary wrote:
> Hi,
>
> It turned out to be a problem with tests and uninitialized memory which I was able to fix with
>
> https://github.com/ceph/ceph/commit/1a9d717d1661e1e9c9eda3749b7d9c8882a995d2
>
> What surprises me is that we did not catch that before. If I remember correctly we ran valgrind and it was clean. Would you have time to review the tests once more to see if you can maybe catch another minor problem ?
>
> Cheers
>
> On 12/02/2015 09:43, Miyamae, Takeshi wrote:
>> Hi Loic,
>>
>>> I would be grateful if you could verify that it works as intended.
>>
>> We have tried create and check actions once for each. It seems it works well.
>> Is that enough for your job?
>>
>> Best regards,
>> Takeshi Miyamae
>>
>> -----Original Message-----
>> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Loic Dachary
>> Sent: Wednesday, February 11, 2015 9:28 PM
>> To: Miyamae, Takeshi/宮前 剛
>> Cc: Ceph Development
>> Subject: SHEC updates to the erasure code non regression corpus
>>
>> Hi,
>>
>> I've updated the erasure code corpus that verifies the encoding of erasure coded chunks do not change over time with a version that includes the SHEC erasure code plugin.
>>
>> https://github.com/ceph/ceph-erasure-code-corpus/commit/498b0102955b747813182734e13e75195f2a02a9
>>
>> From now on it will run each time someone does "make check", but only if the sources are after
>>
>> $ git rev-parse v0.92-988-g7df0556
>> 7df0556210be3afdc02e2ca41b3a3b60569b753a
>>
>> I would be grateful if you could verify that it works as intended. The process for updating the corpus has been documented at https://github.com/ceph/ceph-erasure-code-corpus#ceph-erasure-code-corpus : it was difficult to guess how it works ;-)
>>
>> Cheers
>>
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-02-12 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 12:28 SHEC updates to the erasure code non regression corpus Loic Dachary
2015-02-12 8:43 ` Miyamae, Takeshi
2015-02-12 9:13 ` Loic Dachary
2015-02-12 9:21 ` Loic Dachary [this message]
2015-02-12 9:14 ` Loic Dachary
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=54DC70A6.5040108@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=miyamae.takeshi@jp.fujitsu.com \
--cc=nakao.takanori@jp.fujitsu.com \
--cc=shiozawa.kennsu@jp.fujitsu.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