CEPH filesystem development
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Yuri Weinstein <yuri.weinstein@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: ceph-qa analysis output
Date: Sun, 18 Jan 2015 11:35:35 +0100	[thread overview]
Message-ID: <54BB8C77.7080208@dachary.org> (raw)
In-Reply-To: <CAJBxG-v8+jWxaVpCspv72DPjXfO+7+FeFZr2y+6umsh9xD22=A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2399 bytes --]

Hi Yuri,

I did not know about scrape. It looks extremely useful, thanks ! Do you have more magic items in your bag ? ;-)

Cheers

P.S. And thanks to John for writing scrape :-)

On 18/01/2015 01:27, Yuri Weinstein wrote:
> Sounds good, Loic
> 
> Are you aware BTW about scrape tool written by John Spray?
> https://github.com/jcsp/scrape
> 
> I use it for test runs analysis often.
> 
> Just FYI
> 
> Thx
> YuriW
> 
> On Sat, Jan 17, 2015 at 3:27 PM, Loic Dachary <loic@dachary.org> wrote:
>>
>>
>> On 17/01/2015 23:08, Yuri Weinstein wrote:
>>> Hi Loic,
>>>
>>> I'd love to.
>>>
>>> Let's chat on Monday to finalize format.
>>>
>>> (
>>> PS:  I think format would be easier to maintain like new lines enforced, e,g.
>>>
>>> '701575', '701576', '701582', '701590'
>>>  ttp://tracker.ceph.com/issues/10543
>>> FAILED assert(m_seed < old_pg_num
>>
>> Yes, as long as it's consistent enough to be machine readable, that works :-)
>>
>>>
>>> PPS: Again this ticket http://tracker.ceph.com/issues/10455 would be
>>> helpful in what we are discussing here.
>>>
>>
>> I'm not sure where the output of such a parsing would go. The update redmine API is currently broken (the read API works ok) but if it was fixed the tickets could be updated indeed.
>>
>> Cheers
>>
>>> Thx
>>> YuriW
>>>
>>> On Sat, Jan 17, 2015 at 5:07 AM, Loic Dachary <loic@dachary.org> wrote:
>>>> Hi Yuri,
>>>>
>>>> It would be great if the analysis you compile daily was machine readable. For instance, in a mail you sent to ceph-qa I read
>>>>
>>>> '701575', '701576', '701582', '701590' - known issue
>>>> http://tracker.ceph.com/issues/10543
>>>>
>>>> "FAILED assert(m_seed < old_pg_num)"
>>>>
>>>> (duplicate of http://tracker.ceph.com/issues/10430)
>>>>
>>>> which could be something like:
>>>>
>>>> '701575', '701576', '701582', '701590': http://tracker.ceph.com/issues/10543 FAILED assert(m_seed < old_pg_num)
>>>>
>>>> or any other format you find easier to use consistently.
>>>>
>>>> The reason I ask is because it would help me write a script that associates redmine tickets to your findings, in the context of backporting. It's just an idea, not a request ;-)
>>>>
>>>> Cheers
>>>>
>>>> --
>>>> Loïc Dachary, Artisan Logiciel Libre
>>>>
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>>

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2015-01-18 10:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17 13:07 ceph-qa analysis output Loic Dachary
2015-01-17 22:08 ` Yuri Weinstein
2015-01-17 23:27   ` Loic Dachary
2015-01-18  0:27     ` Yuri Weinstein
2015-01-18 10:35       ` Loic Dachary [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=54BB8C77.7080208@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yuri.weinstein@inktank.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