CEPH filesystem development
 help / color / mirror / Atom feed
* CephFS and the next infernalis release v9.2.1
@ 2016-02-12  7:36 Abhishek Varshney
  2016-02-12 18:13 ` Gregory Farnum
  0 siblings, 1 reply; 3+ messages in thread
From: Abhishek Varshney @ 2016-02-12  7:36 UTC (permalink / raw)
  To: gfarnum; +Cc: Ceph Development, Loic Dachary

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
?

Thanks
Abhishek

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: CephFS and the next infernalis release v9.2.1
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Gregory Farnum @ 2016-02-12 18:13 UTC (permalink / raw)
  To: Abhishek Varshney; +Cc: Ceph Development, Loic Dachary

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. :)
-Greg

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: CephFS and the next infernalis release v9.2.1
  2016-02-12 18:13 ` Gregory Farnum
@ 2016-02-13  1:33   ` Loic Dachary
  0 siblings, 0 replies; 3+ messages in thread
From: Loic Dachary @ 2016-02-13  1:33 UTC (permalink / raw)
  To: Gregory Farnum, Abhishek Varshney; +Cc: Ceph Development



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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-02-13  1:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox