From: Yuri Weinstein <yweinste@redhat.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: teuthology job priorities
Date: Thu, 28 May 2015 12:21:49 -0400 (EDT) [thread overview]
Message-ID: <613662148.8423810.1432830109340.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5566E0AD.80401@dachary.org>
I usually use:
priority [90,100]
for point releases validations.
This is a good thread to bring up for open approval/disapproval.
Does that sound reasonable ??
Thx
YuriW
----- Original Message -----
From: "Loic Dachary" <loic@dachary.org>
To: "Ceph Development" <ceph-devel@vger.kernel.org>
Sent: Thursday, May 28, 2015 2:32:29 AM
Subject: teuthology job priorities
Hi,
This morning I'll schedule a job with priority 50, assuming nobody will get mad at me for using such a low priority because the associated bug fix blocks the release of v0.94.2 (http://tracker.ceph.com/issues/11546) and also assuming noone uses a priority lower than 100 just to get in front of the nightlies[1]. In my imagination
priority [0,100] is for emergencies
priority [100,1000] is to schedule a job with higher priority than the nightlies
priority 1000 (the default) is for all automated tests and no human being wait on them (the nightlies for instance).
Does someone have a different mapping in mind ?
Cheers
[1] the nightlies http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_monitor_the_automated_tests_AKA_nightlies
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-28 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 9:32 teuthology job priorities Loic Dachary
2015-05-28 16:21 ` Yuri Weinstein [this message]
2015-05-28 18:04 ` Gregory Farnum
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=613662148.8423810.1432830109340.JavaMail.zimbra@redhat.com \
--to=yweinste@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.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.