From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <gfarnum@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
Nathan Cutler <ncutler@suse.cz>
Subject: Re: CephFS and the next hammer release v0.94.6
Date: Mon, 8 Feb 2016 12:10:18 +0700 [thread overview]
Message-ID: <56B8233A.5050207@dachary.org> (raw)
In-Reply-To: <CAJ4mKGZx3q840YkZjege0z+OAAm3qHjJTd_PuzGnR2aeLyY-gw@mail.gmail.com>
Hi,
I will run a single job with https://github.com/ceph/ceph/pull/7501 to verify it does work before merging it. Will that be enough ?
Cheers
On 08/02/2016 10:44, Gregory Farnum wrote:
> Yes, just wanted those two fixes we discussed. :)
>
> On Sun, Feb 7, 2016 at 7:43 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Greg,
>>
>> Do you think the hammer branch is ready for QE to start their own round of testing ?
>>
>> Cheers
>>
>> On 04/02/2016 12:44, Loic Dachary wrote:
>>> Hi Greg,
>>>
>>> On 03/02/2016 16:23, Gregory Farnum wrote:
>>>> On Tue, Feb 2, 2016 at 8:52 PM, Loic Dachary <loic@dachary.org> wrote:
>>>>> Hi Greg,
>>>>>
>>>>> The next hammer release as found at https://github.com/ceph/ceph/tree/hammer passed the fs suite (http://tracker.ceph.com/issues/13356#note-25). A more recent run showed 3 failures and I'm not sure how to interpret them ( http://pulpito.ceph.com/loic-2016-01-29_03:02:05-fs-hammer---basic-multi/ ).
>>>>>
>>>>> Do you think the hammer branch is ready for QE to start their own round of testing ? Or should the above errors be investigated first ?
>>>>
>>>> Well, one of them looks to be an infrastructure issue of some kind.
>>>> You appear to have figured out the fsstress one
>>>> (http://tracker.ceph.com/issues/14584#change-65185), and the fsx one
>>>> is http://tracker.ceph.com/issues/14384. I'd get that quick backport
>>>
>>> Thanks for the pointer :-) (and to Nathan for backporting).
>>>
>>>> in as well (it's just a change to the qa script to point at a working
>>>> version of the repo).
>>>
>>> Do you think the hammer branch is ready for QE to start their own round of testing ?
>>>
>>> Cheers
>>>
>>>> -Greg
>>>> --
>>>> 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
>>>>
>>>
>>
>> --
>> 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
next prev parent reply other threads:[~2016-02-08 5:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 4:52 CephFS and the next hammer release v0.94.6 Loic Dachary
2016-02-03 9:23 ` Gregory Farnum
2016-02-03 9:39 ` Nathan Cutler
2016-02-04 5:44 ` Loic Dachary
2016-02-08 3:43 ` Loic Dachary
2016-02-08 3:44 ` Gregory Farnum
2016-02-08 5:10 ` Loic Dachary [this message]
2016-02-08 5:15 ` Gregory Farnum
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=56B8233A.5050207@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.com \
--cc=ncutler@suse.cz \
/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.