Project

General

Profile

Actions

Feature #12526

closed

Setting priority field through arvados-cwl-runner

Added by Bryan Cosca almost 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
10/31/2017
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
0.5
Release relationship:
Auto

Description

I would like a --priority flag that will pass a priority number to the rest of the pipeline, for new jobs that spawn.


Subtasks 2 (0 open2 closed)

Task #13150: Add --priorityResolvedPeter Amstutz10/31/2017

Actions
Task #13151: Review 12526-cwl-priorityResolvedPeter Amstutz10/31/2017

Actions
Actions #1

Updated by Tom Morris almost 5 years ago

  • Target version set to To Be Groomed
Actions #2

Updated by Tom Morris almost 5 years ago

  • Story points set to 0.5
Actions #3

Updated by Tom Morris almost 5 years ago

  • Target version changed from To Be Groomed to Arvados Future Sprints
Actions #4

Updated by Tom Morris over 4 years ago

  • Assigned To set to Peter Amstutz
  • Target version changed from Arvados Future Sprints to 2018-03-14 Sprint
Actions #5

Updated by Lucas Di Pentima over 4 years ago

  • File sdk/cwl/arvados_cwl/__init__.py - Lines 425 & 672: Do you think default priotity = 500 would be convenient to express it as a constant just in case it’s changed in the future?
  • Should the priority range be checked?
Actions #6

Updated by Peter Amstutz over 4 years ago

Lucas Di Pentima wrote:

  • File sdk/cwl/arvados_cwl/__init__.py - Lines 425 & 672: Do you think default priotity = 500 would be convenient to express it as a constant just in case it’s changed in the future?

Fixed.

  • Should the priority range be checked?

Fixed.

12526-cwl-priority @ 6906707ffcbf0f063ab2a802b567f1f91a2fe84a

Actions #8

Updated by Lucas Di Pentima over 4 years ago

This LGTM, please merge.

Actions #9

Updated by Peter Amstutz over 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 50 to 100
Actions #10

Updated by Peter Amstutz over 4 years ago

  • Status changed from Resolved to Feedback

Eh, I broke the --version option with the fix for #12410. Oops.

Actions #11

Updated by Peter Amstutz over 4 years ago

  • Status changed from Feedback to Resolved

Now it is fixed.

Actions #12

Updated by Tom Morris about 4 years ago

  • Release set to 17
Actions

Also available in: Atom PDF