From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sweil@redhat.com>
Cc: Samuel Just <sjust@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: teuthology rados runs for next
Date: Tue, 21 Jul 2015 17:42:37 +0200 [thread overview]
Message-ID: <55AE686D.2010802@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1507210642560.8878@cobra.newdream.net>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
Ok !
teuthology-kill -m multi -r teuthology-2015-07-18_21:00:09-rados-next-distro-basic-multi
teuthology-kill -m multi -r teuthology-2015-07-20_21:00:09-rados-next-distro-basic-multi
I observed that the older
http://pulpito.ceph.com/teuthology-2015-07-17_21:00:10-rados-next-distro-basic-multi
is half way through but does not seem to make progress while the one scheduled today
http://pulpito.ceph.com/teuthology-2015-07-19_21:00:10-rados-next-distro-basic-multi
has one job running. Do you think best to kill the newer so it does not compete for resources that would prevent the older from finishing ? I'd be tempted to kill the newer because it's so difficult to get jobs running right now that it makes sense to preserve a run that already managed to pass > 100 jobs :-)
Cheers
On 21/07/2015 15:43, Sage Weil wrote:
> On Tue, 21 Jul 2015, Loic Dachary wrote:
>> Hi Sam,
>>
>> I noticed today that http://pulpito.ceph.com/?suite=rados&branch=next is
>> lagging three days behind. Do we want to keep all the runs or should we
>> kill the older ones ? I suppose there would be value in having the
>> results for all of them but given the current load in the sepia lab it
>> also significantly delays them. What do you think ?
>
> I think it's better to kill old scheduled runs.
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-07-21 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 8:44 teuthology rados runs for next Loic Dachary
2015-07-21 13:43 ` Sage Weil
2015-07-21 15:42 ` Loic Dachary [this message]
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=55AE686D.2010802@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sjust@redhat.com \
--cc=sweil@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.