ceph-qa analysis output

ceph-qa analysis output

[Loic Dachary]

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

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


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

Re: ceph-qa analysis output

[Yuri Weinstein]

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

<jobs,...>
<issue RE>
<description>  (this I suppose can be retrieved from tracker, a?  if
yes, we may not need it at all)
)

Would it be possible to feed output of those machine digested emails
(and hopefully others) into this doc -
https://docs.google.com/a/inktank.com/spreadsheets/d/1S01gkuA149U5XSLStuzEoh-14tK2ICGm5tsCUomuzTo/edit#gid=403616374
(I granted you access as it's still under development/review) ?


PPS: Again this ticket http://tracker.ceph.com/issues/10455 would be
helpful in what we are discussing here.

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
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: ceph-qa analysis output

[Loic Dachary]

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



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


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

Re: ceph-qa analysis output

[Yuri Weinstein]

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
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: ceph-qa analysis output

[Loic Dachary]

[-- 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 --]