From: Loic Dachary <loic@dachary.org>
To: Jason Dillaman <dillaman@redhat.com>
Cc: Josh Durgin <jdurgin@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: RBD tests on the next dumpling release
Date: Fri, 06 Feb 2015 15:17:39 +0100 [thread overview]
Message-ID: <54D4CD03.8000806@dachary.org> (raw)
In-Reply-To: <1050495133.7647881.1423231520223.JavaMail.zimbra@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Hi Jason,
Thanks for taking time to check :-)
http://tracker.ceph.com/issues/9854 is indeed in the list of issues that need backporting for dumpling:
http://workbench.dachary.org/ceph/ceph-backports/wikis/dumpling#issues-that-need-backporting
so is http://tracker.ceph.com/issues/10299. I'm happy to do another round of testing if you think these two need to be in the next release. Otherwise they will be in the next point release. I'm hopeful we'll be able to do more frequent point releases in the future.
On 06/02/2015 15:05, Jason Dillaman wrote:> I'll take a look at it today, but my gut tells me it probably has something to do w/ a new version of QEMU (assuming the binary isn't source controlled). On a semi-related note, I just discovered that http://tracker.ceph.com/issues/9854 is missing a dumpling backport request. I'll get a dumpling pull request for that issue ASAP.
>
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-02-06 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 22:30 RBD tests on the next dumpling release Loic Dachary
2015-02-06 14:05 ` Jason Dillaman
2015-02-06 14:17 ` Loic Dachary [this message]
2015-02-06 14:42 ` Jason Dillaman
2015-02-09 10:12 ` Loic Dachary
2015-02-09 20:27 ` Jason Dillaman
2015-02-10 0:08 ` Josh Durgin
2015-02-10 7:51 ` 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=54D4CD03.8000806@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dillaman@redhat.com \
--cc=jdurgin@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.