runners: Renamed -a/--all -> --force

Test/bench filters have proven to be mostly non-optional, protecting
against bad configuration that doesn't make any sense.

It's still valid to want to override test filters sometimes, but using a
more, uh, forceful verb probably makes sense here.

The shortform would conflict with -f/--fail, so no shortform flag for
this, but some argue --force should never have a shortform flag anyways.
This commit is contained in:
Christopher Haster
2025-11-16 15:36:06 -06:00
parent efdcb912f5
commit 9728cda682
4 changed files with 34 additions and 34 deletions
+3 -3
View File
@@ -717,8 +717,8 @@ def find_runner(runner, id=None, main=True, **args):
# other context
if args.get('define_depth'):
cmd.append('--define-depth=%s' % args['define_depth'])
if args.get('all'):
cmd.append('-a')
if args.get('force'):
cmd.append('--force')
# only one thread should write to disk/trace, otherwise the output
# ends up clobbered and useless
@@ -1616,7 +1616,7 @@ if __name__ == "__main__":
'--define-depth',
help="How deep to evaluate recursive defines before erroring.")
bench_parser.add_argument(
'-a', '--all',
'--force',
action='store_true',
help="Ignore bench filters.")
bench_parser.add_argument(
+3 -3
View File
@@ -737,8 +737,8 @@ def find_runner(runner, id=None, main=True, **args):
cmd.append('--define-depth=%s' % args['define_depth'])
if args.get('powerloss'):
cmd.append('-P%s' % args['powerloss'])
if args.get('all'):
cmd.append('-a')
if args.get('force'):
cmd.append('--force')
# only one thread should write to disk/trace, otherwise the output
# ends up clobbered and useless
@@ -1639,7 +1639,7 @@ if __name__ == "__main__":
'-P', '--powerloss',
help="Comma-separated list of power-loss scenarios to test.")
test_parser.add_argument(
'-a', '--all',
'--force',
action='store_true',
help="Ignore test filters.")
test_parser.add_argument(