This repository has been archived by the owner on Oct 24, 2020. It is now read-only.
Remove need to specify cpu_units for a step when max is desired #20
Assignees
Labels
Comments
bbangert
added a commit
that referenced
this issue
Mar 20, 2017
We not allocate sufficient cpu units to ensure distinct task placement across the cluster without forcing the test plan to take it into account. Closes #20
bbangert
added a commit
that referenced
this issue
Mar 20, 2017
We not allocate sufficient cpu units to ensure distinct task placement across the cluster without forcing the test plan to take it into account. Closes #20
bbangert
added a commit
that referenced
this issue
Mar 20, 2017
We not allocate sufficient cpu units to ensure distinct task placement across the cluster without forcing the test plan to take it into account. Closes #20
bbangert
added a commit
that referenced
this issue
Mar 20, 2017
We not allocate sufficient cpu units to ensure distinct task placement across the cluster without forcing the test plan to take it into account. Closes #20
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now the CPU units needs to be specified for a step, ideally not specifying the CPU units should choose the maximum available for that instance type.
The text was updated successfully, but these errors were encountered: