From: Loic Dachary <loic@dachary.org>
To: Abhishek L <abhishek.lekshmanan@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Giant backport tasks
Date: Sat, 28 Mar 2015 11:46:40 +0100 [thread overview]
Message-ID: <55168690.2060603@dachary.org> (raw)
In-Reply-To: <87zj6x3c49.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
[cc'ing ceph-devel for archive]
On 28/03/2015 06:49, Abhishek L wrote:
> Hi Loic,
>
> I've started looking into the pending runs for giant. The rados suites
> came out green,
\o/
> rgw seems to have hit a bug, updated this in the
> tracker,
Reading http://tracker.ceph.com/issues/11153#rgw I suggest you use the method described at http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_describe_a_test_result
$ python ../fail.py loic-2015-03-27_08:40:06-rgw-giant---basic-multi
** *'mkdir -p -- /home/ubuntu/cephtest/mnt.0/client.0/tmp && cd -- /home/ubuntu/cephtest/mnt.0/client.0/tmp && CEPH_CLI_TEST_DUP_COMMAND=1 CEPH_REF=90b37d9bdcc044e26f978632cd68f19ece82d19a TESTDIR="/home/ubuntu/cephtest" CEPH_ID="0" PATH=$PATH:/usr/sbin adjust-ulimits ceph-coverage /home/ubuntu/cephtest/archive/coverage timeout 3h /home/ubuntu/cephtest/workunit.client.0/rgw/s3_bucket_quota.pl'*
*** "rgw/multifs/{clusters/fixed-2.yaml frontend/civetweb.yaml fs/xfs.yaml rgw_pool_type/replicated.yaml tasks/rgw_bucket_quota.yaml}":http://pulpito.ceph.com/loic-2015-03-27_08:40:06-rgw-giant---basic-multi/824286
When you have a single bug it's marginally useful but it helps a lot when you have more than a dozen.
> some time on why the radosgw hit a bug a little more
> so that I can get to the cause of this.
Great, looking forward to read about it at http://tracker.ceph.com/issues/11259 ;-)
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
parent reply other threads:[~2015-03-28 10:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87zj6x3c49.fsf@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=55168690.2060603@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.lekshmanan@gmail.com \
--cc=ceph-devel@vger.kernel.org \
/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.