From: Loic Dachary <loic@dachary.org>
To: Andrew Schoen <aschoen@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: teuthology-suite and priorities
Date: Fri, 27 Mar 2015 09:07:26 +0100 [thread overview]
Message-ID: <55150FBE.9070604@dachary.org> (raw)
In-Reply-To: <5510211F.3020007@dachary.org>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
Hi Andrew,
I still do not understand what I missed with priorities but I re-scheduled
http://pulpito.ceph.com/loic-2015-03-27_09:03:04-rados-giant---basic-multi
http://pulpito.ceph.com/loic-2015-03-27_09:01:25-rados-giant---basic-multi
http://pulpito.ceph.com/loic-2015-03-27_08:40:06-rgw-giant---basic-multi
with priority 1000. Let see if it runs before the nightlies again or if it behaves ;-)
Cheers
On 23/03/2015 15:20, Loic Dachary wrote:
> Hi,
>
> When scheduling suites that are low priority (giant for instance at http://pulpito.ceph.com/loic-2015-03-23_01:09:31-rados-giant---basic-multi/), the --priority 1000 is set because (if I remember correctly) this is the standard priority for nightlies. However, it seems to be different because this morning the giant suite was running although a hammer suite was scheduled before it (for instance http://pulpito.ceph.com/teuthology-2015-03-22_23:18:01-multimds-hammer-testing-basic-multi/) and was still waiting.
>
> The giant suite was killed so that it does not interfere with more urgent jobs. Looking at the teuthology jobs there does not seem to be a trace of the priority, probably stored elsewhere.
>
> I would be very grateful if you could explain how priorities should be used.
>
> Cheers
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-03-27 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 14:20 teuthology-suite and priorities Loic Dachary
2015-03-23 14:24 ` Gregory Farnum
2015-03-23 14:35 ` Loic Dachary
2015-03-27 8:07 ` 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=55150FBE.9070604@dachary.org \
--to=loic@dachary.org \
--cc=aschoen@redhat.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.