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 07:34:04 +0100 [thread overview]
Message-ID: <54DEEC5C.4030605@dachary.org> (raw)
In-Reply-To: <CAC6JEv9pUeCtjs_SBeqr5N=4aSUUuUsbDW3eMipVsBTq5AkZkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2068 bytes --]
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
* read the ceph-qa reports daily
* for each failed job, either relate it to an issue or create one or declare it noise
* 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
* bi-weekly bug scrub makes sure no issue, old or new, is forgotten
* 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
Cheers
On 13/02/2015 20:29, Gregory Farnum wrote:
> On Thu, Feb 12, 2015 at 7:58 PM,
> <teuthworker@teuthology.front.sepia.ceph.com> wrote:
>> Test Run: teuthology-2015-02-11_16:13:01-samba-giant-distro-basic-multi
>> =================================================================
>> info: http://pulpito.ceph.com/teuthology-2015-02-11_16:13:01-samba-giant-distro-basic-multi/
>> logs: http://qa-proxy.ceph.com/teuthology/teuthology-2015-02-11_16:13:01-samba-giant-distro-basic-multi/
>> failed: 0
>> hung: 1
>> passed: 11
>>
>> Hung
>> =================================================================
>> [752393] samba/{clusters/samba-basic.yaml debug/mds_client.yaml fs/btrfs.yaml install/install.yaml mount/noceph.yaml workload/smbtorture.yaml}
>> info: http://pulpito.ceph.com/teuthology-2015-02-11_16:13:01-samba-giant-distro-basic-multi/752393/
>
> Looks like http://tracker.ceph.com/issues/10413, the upstream fix for
> which should be trickling down soon.
>
>>
>> Passed
>> =================================================================
> _______________________________________________
> Ceph-qa mailing list
> Ceph-qa@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-qa-ceph.com
>
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next parent reply other threads:[~2015-02-14 7:45 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 ` Loic Dachary [this message]
2015-02-14 7:56 ` [Ceph-qa] 1 hung, 11 passed in teuthology-2015-02-11_16:13:01-samba-giant-distro-basic-multi Gregory Farnum
2015-02-14 10:31 ` Loic Dachary
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=54DEEC5C.4030605@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox