Suggested teuthology priority

List overview All Threads
Download

newer

older

Ceph Build Error

Ceph Leadership Team meeting...

Patrick Donnelly

11 Sep 2019 11 Sep '19

2:48 p.m.

For developers submitting jobs using teuthology, we now have recommendations on what priority level to use: https://docs.ceph.com/docs/master/dev/developer_guide/#testing-priority -- Patrick Donnelly, Ph.D. He / Him / His Senior Software Engineer Red Hat Sunnyvale, CA GPG: 19F28A586F808C2402351B93C3301A3E258DD79D

Show replies by thread

Rishabh Dave

11 Sep 11 Sep

6:22 p.m.

On Wed, 11 Sep 2019 at 19:19, Patrick Donnelly <pdonnell(a)redhat.com> wrote:

...

For developers submitting jobs using teuthology, we now have recommendations on what priority level to use: https://docs.ceph.com/docs/master/dev/developer_guide/#testing-priority

Normally, I was told to the keep priority number above 100 or around 90. But it looks like the recommended number for testing my PRs would be between 50 and 75. Is my understanding correct?

Jos Collin

12 Sep 12 Sep

12:56 a.m.

On 11/09/19 10:52 PM, Rishabh Dave wrote:

...

On Wed, 11 Sep 2019 at 19:19, Patrick Donnelly <pdonnell(a)redhat.com> wrote:

For developers submitting jobs using teuthology, we now have recommendations on what priority level to use: https://docs.ceph.com/docs/master/dev/developer_guide/#testing-priority

Normally, I was told to the keep priority number above 100 or around 90. But it looks like the recommended number for testing my PRs would be between 50 and 75. Is my understanding correct?

Yes, if your feature/fix is "running fewer than about 25 jobs" > _______________________________________________ > Dev mailing list -- dev(a)ceph.io > To unsubscribe send an email to dev-leave(a)ceph.io >

Casey Bodley

16 Mar 16 Mar

7:59 p.m.

...

On 11/09/19 10:52 PM, Rishabh Dave wrote:

On Wed, 11 Sep 2019 at 19:19, Patrick Donnelly <pdonnell(a)redhat.com> wrote:

For developers submitting jobs using teuthology, we now have recommendations on what priority level to use: https://docs.ceph.com/docs/master/dev/developer_guide/#testing-priority

Normally, I was told to the keep priority number above 100 or around 90. But it looks like the recommended number for testing my PRs would be between 50 and 75. Is my understanding correct?

Yes, if your feature/fix is "running fewer than about 25 jobs"

_______________________________________________ Dev mailing list -- dev(a)ceph.io To unsubscribe send an email to dev-leave(a)ceph.io

Yuri Weinstein

8:05 p.m.

I we use priority 100-150 for point releases, we will never be able to make them on time! On Thu, Mar 16, 2023 at 12:59 PM Casey Bodley <cbodley(a)redhat.com> wrote:

...

On 11/09/19 10:52 PM, Rishabh Dave wrote:

On Wed, 11 Sep 2019 at 19:19, Patrick Donnelly <pdonnell(a)redhat.com> wrote:

For developers submitting jobs using teuthology, we now have recommendations on what priority level to use: https://docs.ceph.com/docs/master/dev/developer_guide/#testing-priority

Normally, I was told to the keep priority number above 100 or around 90. But it looks like the recommended number for testing my PRs would be between 50 and 75. Is my understanding correct?

Yes, if your feature/fix is "running fewer than about 25 jobs"

_______________________________________________ Dev mailing list -- dev(a)ceph.io To unsubscribe send an email to dev-leave(a)ceph.io

Casey Bodley

8:17 p.m.

if everyone was following those guidelines, that shouldn't be a problem. if you still feel the guidelines need to be adjusted, feel free to open a pull request for discussion On Thu, Mar 16, 2023 at 4:05 PM Yuri Weinstein <yweinste(a)redhat.com> wrote:

...

I we use priority 100-150 for point releases, we will never be able to make them on time! On Thu, Mar 16, 2023 at 12:59 PM Casey Bodley <cbodley(a)redhat.com> wrote:

On 11/09/19 10:52 PM, Rishabh Dave wrote:

On Wed, 11 Sep 2019 at 19:19, Patrick Donnelly <pdonnell(a)redhat.com> wrote: > > For developers submitting jobs using teuthology, we now have > recommendations on what priority level to use: > https://docs.ceph.com/docs/master/dev/developer_guide/#testing-priority Normally, I was told to the keep priority number above 100 or around 90. But it looks like the recommended number for testing my PRs would be between 50 and 75. Is my understanding correct?

Yes, if your feature/fix is "running fewer than about 25 jobs"

_______________________________________________ Dev mailing list -- dev(a)ceph.io To unsubscribe send an email to dev-leave(a)ceph.io

Yuri Weinstein

8:31 p.m.

Who is enforcing those guidelines? On Thu, Mar 16, 2023 at 1:17 PM Casey Bodley <cbodley(a)redhat.com> wrote:

...

I we use priority 100-150 for point releases, we will never be able to make them on time! On Thu, Mar 16, 2023 at 12:59 PM Casey Bodley <cbodley(a)redhat.com> wrote:

On 11/09/19 10:52 PM, Rishabh Dave wrote: > On Wed, 11 Sep 2019 at 19:19, Patrick Donnelly <pdonnell(a)redhat.com> wrote: >> >> For developers submitting jobs using teuthology, we now have >> recommendations on what priority level to use: >> https://docs.ceph.com/docs/master/dev/developer_guide/#testing-priority > > Normally, I was told to the keep priority number above 100 or around > 90. But it looks like the recommended number for testing my PRs would > be between 50 and 75. Is my understanding correct? Yes, if your feature/fix is "running fewer than about 25 jobs" > _______________________________________________ > Dev mailing list -- dev(a)ceph.io > To unsubscribe send an email to dev-leave(a)ceph.io > _______________________________________________ Dev mailing list -- dev(a)ceph.io To unsubscribe send an email to dev-leave(a)ceph.io

_______________________________________________ Dev mailing list -- dev(a)ceph.io To unsubscribe send an email to dev-leave(a)ceph.io

Casey Bodley

9:11 p.m.

if we wanted to be strict about it, we could remove the --force-priority option entirely. but it exists for emergencies, and i'm fine leaving that to an honor system. as an open source community, a lot of our processes are inherently social. i'm just trying to raise awareness that we have these guidelines, so they can be used to resolve disputes over the use of priorities On Thu, Mar 16, 2023 at 4:32 PM Yuri Weinstein <yweinste(a)redhat.com> wrote:

...

Who is enforcing those guidelines? On Thu, Mar 16, 2023 at 1:17 PM Casey Bodley <cbodley(a)redhat.com> wrote:

I we use priority 100-150 for point releases, we will never be able to make them on time! On Thu, Mar 16, 2023 at 12:59 PM Casey Bodley <cbodley(a)redhat.com> wrote:

a friendly reminder about these priority guidelines in https://docs.ceph.com/en/latest/dev/developer_guide/testing_integration_tes… the queue has been backed up with thousands of jobs scheduled below priority 75. please be considerate when using '--force-priority' option to schedule suites On Wed, Sep 11, 2019 at 7:56 PM Jos Collin <jcollin(a)redhat.com> wrote: > > > > On 11/09/19 10:52 PM, Rishabh Dave wrote: > > On Wed, 11 Sep 2019 at 19:19, Patrick Donnelly <pdonnell(a)redhat.com> wrote: > >> > >> For developers submitting jobs using teuthology, we now have > >> recommendations on what priority level to use: > >> https://docs.ceph.com/docs/master/dev/developer_guide/#testing-priority > > > > Normally, I was told to the keep priority number above 100 or around > > 90. But it looks like the recommended number for testing my PRs would > > be between 50 and 75. Is my understanding correct? > > Yes, if your feature/fix is "running fewer than about 25 jobs" > > > _______________________________________________ > > Dev mailing list -- dev(a)ceph.io > > To unsubscribe send an email to dev-leave(a)ceph.io > > > _______________________________________________ > Dev mailing list -- dev(a)ceph.io > To unsubscribe send an email to dev-leave(a)ceph.io _______________________________________________ Dev mailing list -- dev(a)ceph.io To unsubscribe send an email to dev-leave(a)ceph.io

405

days inactive

1687

days old

dev@ceph.io

Manage subscription

7 comments

5 participants

tags (0)

participants (5)

Casey Bodley
Jos Collin
Patrick Donnelly
Rishabh Dave
Yuri Weinstein