From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <greg@gregs42.com>
Cc: Andrew Schoen <aschoen@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: teuthology-suite and priorities
Date: Mon, 23 Mar 2015 15:35:34 +0100 [thread overview]
Message-ID: <551024B6.5000201@dachary.org> (raw)
In-Reply-To: <CAC6JEv_zJFVGf38NE7gJTXXA244adPy3jr3Gb+-oPNnnmck-MQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1881 bytes --]
Hi Greg,
On 23/03/2015 15:24, Gregory Farnum wrote:
> On Mon, Mar 23, 2015 at 7:20 AM, Loic Dachary <loic@dachary.org> 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.
>
> I've seen a couple of oddities with suites that you've scheduled
> before, and I think something in the system might not be using
> timestamps properly. :) Also, the multimds suite is not an important
> one right now, so feel free to zap it rather than an LTS point release
> run in future.
I would not dare zap/kill a LTS point release run ;-)
> 1000 is definitely the default, and I don't have one handy to look at
> right now but I think if you set a non-default priority it will show
> up in one of the config files.
Right ! It shows at http://qa-proxy.ceph.com/teuthology/loic-2015-03-22_18:50:00-rgw-giant-backports---basic-multi/815885/orig.config.yaml (which was a --priority 101 indeed because it was a single job suite for which I wanted results fast).
I'll try to re-schedule with --priority 2000 then hoping it will go last.
Cheers
> -Greg
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-03-23 14:35 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 [this message]
2015-03-27 8:07 ` Loic Dachary
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=551024B6.5000201@dachary.org \
--to=loic@dachary.org \
--cc=aschoen@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@gregs42.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.