All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <greg@gregs42.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [Ceph-qa] 1 hung, 11 passed in teuthology-2015-02-11_16:13:01-samba-giant-distro-basic-multi
Date: Sat, 14 Feb 2015 11:31:00 +0100	[thread overview]
Message-ID: <54DF23E4.9010505@dachary.org> (raw)
In-Reply-To: <CAC6JEv_7OEsLkj1vm65Jxqh4e7LBnTQUAp6r0_5Tbs0-Z=YZZQ@mail.gmail.com>

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



On 14/02/2015 08:56, Gregory Farnum wrote:
> On Fri, Feb 13, 2015 at 10:34 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Greg,
>>
>> I'm curious to know how you handle the flow of mails from QA runs. Here is a wild guess:
>>
>> * from time to time check that the nightlies run the suites that should be run
> 
> Uh, I guess?
> 
>> * read the ceph-qa reports daily
> 
> Yeah
> 
>> * for each failed job, either relate it to an issue or create one or declare it noise
> 
> Yeah
> 
>> * if a job fails on an existing ticket store a link to the job if it's rare occurrence and the cause is not yet known
> 
> Yeah, or just to make clear it's still happening or whatever
> 
>> * bi-weekly bug scrub makes sure no issue, old or new, is forgotten
> 
> Hopefully!
> 
>> * at release time you decide that it is ready based on:
>> ** the list of urgent/immediate issues that you can browse to ensure no issue is a blocker
>> ** the last run of each suite to ensure they are recent enough and environmental noise did not permanently shadow anything
> 
> Yeah. Well, the last run alone isn't so important; we want to see a
> string of clean runs because a lot of issues aren't reproduced in
> every run.

Do you check the string of clean runs with http://pulpito.ceph.com/?suite=fs&branch=giant for instance ? Or do you have a command line that does the same ?

Cheers

> -Greg
> 
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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

  reply	other threads:[~2015-02-14 10:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150213035821.17712282150@teuthology.front.sepia.ceph.com>
     [not found] ` <CAC6JEv9pUeCtjs_SBeqr5N=4aSUUuUsbDW3eMipVsBTq5AkZkQ@mail.gmail.com>
2015-02-14  6:34   ` [Ceph-qa] 1 hung, 11 passed in teuthology-2015-02-11_16:13:01-samba-giant-distro-basic-multi Loic Dachary
2015-02-14  7:56     ` Gregory Farnum
2015-02-14 10:31       ` Loic Dachary [this message]
2015-02-14 16:22       ` Yuri Weinstein
2015-02-14 21:53         ` Loic Dachary
2015-02-14 22:12           ` Loic Dachary
2015-02-14 22:20             ` Yuri Weinstein
2015-02-16  9:35               ` 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=54DF23E4.9010505@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@gregs42.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.