A depressingly high number of autotests have a JOB_RETRIES field with some number greater than 1 in their control file these days (e.g. all FAFT tests). This may be necessary or "good" for the test's normal use in automated integration test suites, but it is very annoying when developing or debugging tests. You usually just want it to run once and then see what went wrong, not wait until all the retries have run that each give you the same result again anyway.

Unfortunately, as far as I can tell there's no easy way to tell test_that to ignore this setting and just run the job once. Can we please add a new command line flag for that (e.g. -n/--no-retries or -r/--retries <overriding number>)? Alternatively, this could also just be thrown in as another effect of the existing --fast flag.