Skip to content

Submission metadata relating to job priority and completion percentages

Aidan Richard Wiederhold requested to merge aiwieder/priority_metadata into master

These changes allow a user to specify a per-job priority and completion percentage, where the latter is the threshold at which a job can be considered complete to prevent problematic files/sites from holding up the whole production.

A comment can be added via a key in the defaults but is not allowed to be added per-job, the comment can be an arbitrary string but a user may need to enclose it in " if using some characters, for example a % symbol.

The priority can only be one of 1a, 1b, 2a, 2b and the completion percentage can be any float from 0. to 100. I don't think 0. should be allowed but I'm not sure of a way to prevent it in regex, I would think a user won't try to say a job is considered finished at 0% progress anyway.

Tests are added for the priority and completion percentages to rule out:

  • Incorrect priorities

  • Integer percentages

  • Percentages greater than 100

  • Negative percentages

  • String percentages

Note that procedures and rules, such as priorities, need to be revisited and are to be discussed in the DPA task https://gitlab.cern.ch/lhcb-dpa/project/-/issues/118.

Edited by Aidan Richard Wiederhold

Merge request reports