From: Loic Dachary <loic@dachary.org>
To: sjust@redhat.com
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: rados and the next giant release
Date: Tue, 10 Feb 2015 16:02:14 +0100 [thread overview]
Message-ID: <54DA1D76.7050206@dachary.org> (raw)
In-Reply-To: <CA+4uBUZEwuSkLyAQZHtgZpjB968KZao8=3D+YBC01z4R2_6=ZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
Cool thanks :-)
On 10/02/2015 15:58, Samuel Just wrote:
> Yeah, that bug only affects shutdown. Ok for QE by me.
> -Sam
>
> On Tue, Feb 10, 2015 at 6:50 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Sam,
>>
>> The rados teuthology suite for the next giant release as found in https://github.com/ceph/ceph/commits/giant-backports came back (it is http://pulpito.ceph.com/loic-2015-02-02_23:31:31-rados-giant-backports---basic-multi) with one error and about 20 environmental errors (see http://tracker.ceph.com/issues/10501#teuthology-run-6b08a729540c61f3c8b15c5a3ce9382634bf800c-february-2015 for a complete list).
>>
>> The error is known : http://tracker.ceph.com/issues/7995 osd shutdown: ./common/shared_cache.hpp: 93: FAILED assert(weak_refs.empty())
>>
>> Do you think it is ready for QE to start their own round of testing ?
>>
>> Cheers
>>
>> P.S. I asked the same question a few weeks ago but a number of rgw patches were added to the giant integration branch in the meantime and I took this opportunity to run an extra round. Hopefully this is the last one :-)
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
parent reply other threads:[~2015-02-10 15:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CA+4uBUZEwuSkLyAQZHtgZpjB968KZao8=3D+YBC01z4R2_6=ZQ@mail.gmail.com>]
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=54DA1D76.7050206@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sjust@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox