From: Varsha Rao Date: Fri, 21 Aug 2020 10:39:33 +0000 (+0530) Subject: doc/developer_guide: Update about '--force-priority' flag X-Git-Tag: v16.1.0~1138^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=d1651ba1d0d6cbb9fbc489e69e4eb681d72275b9;p=ceph.git doc/developer_guide: Update about '--force-priority' flag The '--force-priority' flag is introduced in PR https://github.com/ceph/teuthology/pull/1550. Signed-off-by: Varsha Rao --- diff --git a/doc/dev/developer_guide/tests-integration-tests.rst b/doc/dev/developer_guide/tests-integration-tests.rst index f3fe002b0f8..37c08afc946 100644 --- a/doc/dev/developer_guide/tests-integration-tests.rst +++ b/doc/dev/developer_guide/tests-integration-tests.rst @@ -54,9 +54,7 @@ Nightlies are often half-finished and cancelled due to the volume of testing done so your jobs may never finish. Therefore, it is common to select a priority less than 1000. -Any priority may be selected when submitting jobs. But, in order to be -sensitive to the workings of other developers that also need to do testing, -the following recommendations should be followed: +Job priority should be selected based on the following recommendations: * **Priority < 10:** Use this if the sky is falling and some group of tests must be run ASAP. @@ -85,6 +83,10 @@ In case you don't know how many jobs would be triggered by issue ``teuthology-suite`` command again, this time without ``--dry-run`` and with ``-p`` and an appropriate number as an argument to it. +To skip the priority check, use ``--force-priority``. In order to be sensitive +to the runs of other developers who also need to do testing, please use it in +emergency only. + Suites Inventory ----------------