of jobs exceeds <threshold>. Use 0 to allow
any number [default: {default_job_threshold}].
++=================+=================================================================+
+| Priority | Explanation |
++=================+=================================================================+
+| N < 10 | Use this if the sky is falling and some group of tests |
+| | must be run ASAP. |
++-----------------+-----------------------------------------------------------------+
+| 10 <= N < 50 | Use this if your tests are urgent and blocking other |
+| | important development. |
++-----------------+-----------------------------------------------------------------+
+| 50 <= N < 75 | Use this if you are testing a particular feature/fix |
+| | and running fewer than about 25 jobs. This range is also |
+| | used for urgent release testing. |
++-----------------+-----------------------------------------------------------------+
+| 75 <= N < 100 | Tech Leads regularly schedule integration tests with this |
+| | priority to verify pull requests against master. |
++-----------------+-----------------------------------------------------------------+
+| 100 <= N < 150 | This priority is used for QE validation of point releases. |
++-----------------+-----------------------------------------------------------------+
+| 150 <= N < 200 | Use this priority for 100 jobs or fewer that test a particular |
+| | feature or fix. Results are available in about 24 hours. |
++-----------------+-----------------------------------------------------------------+
+| 200 <= N < 1000 | Use this priority for large test runs. Results are available |
+| | in about a week. |
++-----------------+-----------------------------------------------------------------+
+
""".format(
default_machine_type=config.default_machine_type,
default_results_timeout=config.results_timeout,