All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <greg@gregs42.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: CephFS and the next firefly release
Date: Sat, 28 Feb 2015 15:18:51 +0100	[thread overview]
Message-ID: <54F1CE4B.5020004@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

Hi Greg,

The fs teuthology suite for the next firefly release as found in https://github.com/ceph/ceph/commits/firefly-backports came back with three failures : http://tracker.ceph.com/issues/10641#fs. Do you think it is ready for QE to start their own round of testing ?

Cheers

P.S. I'll include the fs suite as part of the pre-QE round of testing from now on, unless you think it is redundant or not useful.

-- 
Loïc Dachary, Artisan Logiciel Libre






[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2015-02-28 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28 14:18 Loic Dachary [this message]
2015-03-01  5:00 ` CephFS and the next firefly release Gregory Farnum
2015-03-01 10:18   ` Loic Dachary
2015-03-01 16:54     ` 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=54F1CE4B.5020004@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@gregs42.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.