From: Josh Durgin <jdurgin@redhat.com>
To: John Spray <jspray@redhat.com>, Vasu Kulkarni <vakulkar@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
ceph-qa <ceph-qa@ceph.com>
Subject: Re: ceph-qa-suite branching (merge it into ceph.git?)
Date: Wed, 13 Apr 2016 12:08:53 -0700 [thread overview]
Message-ID: <570E9945.6040401@redhat.com> (raw)
In-Reply-To: <CALe9h7f3OFobvNscxMTmoSSkxf2PfG71wPqAJ8mTWEBKpGH3Dw@mail.gmail.com>
On 04/13/2016 11:46 AM, John Spray wrote:
> On Wed, Apr 13, 2016 at 7:02 PM, Vasu Kulkarni <vakulkar@redhat.com> wrote:
>> we also have s3 suites in its own repo, we have big files in ceph.com/qa
>> which i believe is the right place.
>
> I'm a bit ignorant of the s3 tests, is there a particular reason they
> live separately to the main ceph-qa-suite?
s3 tests are more generic. They run against other s3 implementations,
and only a labeled subset work with rgw.
Josh
next prev parent reply other threads:[~2016-04-13 19:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 10:52 ceph-qa-suite branching (merge it into ceph.git?) John Spray
2016-04-13 12:45 ` Sage Weil
[not found] ` <570E4843.8000102@dachary.org>
2016-04-13 13:58 ` [Ceph-qa] " Gregory Farnum
2016-04-13 18:31 ` John Spray
2016-04-13 18:35 ` Samuel Just
2016-04-13 18:38 ` Sage Weil
2016-04-13 18:50 ` John Spray
2016-04-13 18:54 ` Gregory Farnum
2016-04-13 19:00 ` Sage Weil
2016-04-13 19:06 ` Samuel Just
2016-04-13 20:12 ` Josh Durgin
2016-04-13 20:16 ` Samuel Just
[not found] ` <570EB571.10907@dachary.org>
2016-04-13 21:11 ` Samuel Just
2016-04-13 21:17 ` Josh Durgin
2016-04-13 21:59 ` Loic Dachary
[not found] ` <CAKPXa=Y5rJ4ygM9Sdvys+86RwufnKopTOkMNdPHcpCh5bFbQ0w@mail.gmail.com>
2016-04-13 18:10 ` Fwd: " Vasu Kulkarni
2016-04-13 18:23 ` Samuel Just
2016-04-13 18:57 ` Vasu Kulkarni
2016-04-13 18:46 ` John Spray
2016-04-13 19:06 ` Vasu Kulkarni
2016-04-13 19:09 ` [Ceph-qa] " Sage Weil
2016-04-13 19:08 ` Josh Durgin [this message]
2016-04-13 19:18 ` Abhishek Lekshmanan
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=570E9945.6040401@redhat.com \
--to=jdurgin@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-qa@ceph.com \
--cc=jspray@redhat.com \
--cc=vakulkar@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.