schedule: fix first-in-suite option help

The schedule command validates --seed, --subset and
--no-nested-subset together with --first-in-suite, and the suite
runner passes them that way when writing the rerun memo.

Update the help text to match the implemented behavior.

Reported-by: T K Chandra Hasan <t.k.chandra.hasan@ibm.com>
Signed-off-by: Kefu Chai <k.chai@proxmox.com>

diff --git a/scripts/schedule.py b/scripts/schedule.py
index 58f7a46249dfbf0e291824f6420a9fb0cb0abcfd..26a7fe281ef4e274cb92676d38538736c4a917ab 100644 (file)
--- a/scripts/schedule.py
+++ b/scripts/schedule.py
@@ -44,12 +44,12 @@ optional arguments:
                                        finish before emailing results. Only
                                        applies to the last job in a suite.
   --seed <seed>                        The random seed for rerunning the suite.
-                                       Only applies to the last job in a suite.
+                                       Only applies to the first job in a suite.
   --subset <subset>                    The subset option passed to teuthology-suite.
-                                       Only applies to the last job in a suite.
+                                       Only applies to the first job in a suite.
   --no-nested-subset                   The no-nested-subset option passed to
                                        teuthology-suite.
-                                       Only applies to the last job in a suite.
+                                       Only applies to the first job in a suite.
   --dry-run                            Instead of scheduling, just output the
                                        job config.