From: Loic Dachary <loic@dachary.org>
To: Yehuda Sadeh <yehuda@inktank.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Swift tests failing randomly
Date: Sun, 10 Aug 2014 10:46:37 +0200 [thread overview]
Message-ID: <53E7316D.3090808@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
Hi Yehuda,
In the past few months the swift tests failed randomly and I was unfortunately unable to figure out why. Here are a few examples:
http://pulpito.ceph.com/loic-2014-08-08_12:17:30-upgrade:firefly-x:stress-split-wip-9025-chunk-remapping-testing-basic-vps/406944
http://pulpito.ceph.com/loic-2014-08-08_12:17:30-upgrade:firefly-x:stress-split-wip-9025-chunk-remapping-testing-basic-vps/406941
http://pulpito.ceph.com/loic-2014-08-08_12:17:30-upgrade:firefly-x:stress-split-wip-9025-chunk-remapping-testing-basic-vps/406946
http://pulpito.ceph.com/loic-2014-08-08_12:17:30-upgrade:firefly-x:stress-split-wip-9025-chunk-remapping-testing-basic-vps/406947
and it has happened on every upgrade test run since I can remember. I fail to see a pattern and cannot figure out what the real problem is. It would be really great if you could take a look. Even a hunch or a tip would be greatly appreciated :-)
You can find more context in
http://tracker.ceph.com/issues/8988
http://tracker.ceph.com/issues/8016
http://tracker.ceph.com/issues/7799
and discussions at
http://www.spinics.net/lists/ceph-devel/msg19933.html
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next reply other threads:[~2014-08-10 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 8:46 Loic Dachary [this message]
2014-08-11 16:21 ` Swift tests failing randomly Loic Dachary
2014-08-11 17:11 ` Yehuda Sadeh
2014-08-11 17:13 ` Sage Weil
2014-08-11 17:34 ` Yuri Weinstein
2014-08-11 18:47 ` Loic Dachary
2014-08-11 18:50 ` Yuri Weinstein
2014-08-11 18:55 ` Sage Weil
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=53E7316D.3090808@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=yehuda@inktank.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.