Skip to content

Setting qos in env_batch.xml no longer works #6692

Open
ESMCI/cime
#4706
@jonbob

Description

@jonbob

I have been running on chrysalis with the "high" qos by modifying env_batch.xml with the last directive in the following snippet:

    <directives>
      <directive> --job-name={{ job_id }}</directive>
      <directive> --nodes={{ num_nodes }}</directive>
      <directive> --output={{ job_id }}.%j </directive>
      <directive> --exclusive </directive>
      <directive> --qos=high </directive>
    </directives>
    ````
That has worked until recently, but now it seems to be ignored. I can still change the qos of a run after it has been submitted using scontrol, so it's not that chrysalis no longer recognizes it.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions