From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <gfarnum@redhat.com>,
Abhishek Varshney <abhishek.varshney@flipkart.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: CephFS and the next infernalis release v9.2.1
Date: Sat, 13 Feb 2016 08:33:51 +0700 [thread overview]
Message-ID: <56BE87FF.3080307@dachary.org> (raw)
In-Reply-To: <CAJ4mKGaWYit3X2j8bhsZyiG2ODUinAmTjbS6W3uVzHwALHG4Mw@mail.gmail.com>
On 13/02/2016 01:13, Gregory Farnum wrote:
> On Thu, Feb 11, 2016 at 11:36 PM, Abhishek Varshney
> <abhishek.varshney@flipkart.com> wrote:
>> Hi Greg,
>>
>> The next infernalis release as found at
>> https://github.com/ceph/ceph/tree/infernalis passed most of the CephFS
>> suite ( http://tracker.ceph.com/issues/13750#note-19 ) except for 1
>> failure, which was not seen at a later run (
>> http://tracker.ceph.com/issues/13750#note-26 ). Do you think the
>> infernalis branch is ready for QE to start their own round of testing
>> ?
>
> Uh, assuming I'm reading this correctly, you've hit a known
> intermittent bug which happened to show up on one run, but not the
> next.
>
> You can release without the fix (it's not a regression), but please
> realize that we have a lot of intermittent bugs so just because an
> issue doesn't appear in one run doesn't mean the issue is gone. :)
Hi Greg,
We realize there are intermittent bugs. This is why we're asking you to decide wether this specific bug should be a blocker for the release or not. What do you think ?
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
prev parent reply other threads:[~2016-02-13 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 7:36 CephFS and the next infernalis release v9.2.1 Abhishek Varshney
2016-02-12 18:13 ` Gregory Farnum
2016-02-13 1:33 ` 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=56BE87FF.3080307@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.varshney@flipkart.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.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.