Happy Hacktoberfest, Bitcoin!
(this PR doesn't really pursue Hacktoberfest)
Happy Hacktoberfest, Bitcoin!
(this PR doesn't really pursue Hacktoberfest)
Please follow the contributing guidelines. i.e write a proper commit message. Don't use the default GitHub message, it's not useful at all.
343 | @@ -344,7 +344,7 @@ def main(): 344 | parser.add_argument('--keepcache', '-k', action='store_true', help='the default behavior is to flush the cache directory on startup. --keepcache retains the cache from the previous testrun.') 345 | parser.add_argument('--quiet', '-q', action='store_true', help='only print dots, results summary and failure logs') 346 | parser.add_argument('--tmpdirprefix', '-t', default=tempfile.gettempdir(), help="Root directory for datadirs") 347 | - parser.add_argument('--failfast', action='store_true', help='stop execution after the first test failure') 348 | + parser.add_argument('--failfast', '-ff', action='store_true', help='stop execution after the first test failure')
Short options should only be a single character.
utACK
utACK
Please squash your commits (see here if you haven't done this before)
Btw, is this PR for hacktoberfest? (based on your PR description)
343 | @@ -344,7 +344,7 @@ def main(): 344 | parser.add_argument('--keepcache', '-k', action='store_true', help='the default behavior is to flush the cache directory on startup. --keepcache retains the cache from the previous testrun.') 345 | parser.add_argument('--quiet', '-q', action='store_true', help='only print dots, results summary and failure logs') 346 | parser.add_argument('--tmpdirprefix', '-t', default=tempfile.gettempdir(), help="Root directory for datadirs") 347 | - parser.add_argument('--failfast', action='store_true', help='stop execution after the first test failure') 348 | + parser.add_argument('--failfast', '-F', action='store_true', help='stop execution after the first test failure')
Any reason this isn't lowercase, like all the other options?
Lowercase -f would typically be reserved for "force", though... :/
I'm seeing test/functional/wallet_hd.py help (in which the lowercase f is being used as short option) being automatically printed after requesting test/functional/test_runner.py -h.
Using an uppercase F here has been a precaution, but in this occasion I would be keen to switch it to lowercase here and deal with a potential arguments conflict later, once and if I'm sure it can happen.
BTW, it would appeal me to change this lowercase f in test_framework.py to an uppercase D (reserving lowercase d for --descriptors):
https://github.com/bitcoin/bitcoin/blob/446b706696451ae1a66ac416f347d734c5741d7c/test/functional/test_framework/test_framework.py#L203
CC @josibake (168b6c317ca054c1287c36be532964e861f44266)
I would see useful using an "s" for "stop" instead.
meshcollider wrote:
Btw, is this PR for hacktoberfest? (based on your PR description)
Not really, no. I have updated the text accordingly.
Short options should only be a single character. If not, they can't be
concatenated in a single "-word" (from review by luke-jr).
F is chosen instead of f, because f could be reserved to the nested
wallet_hd.py (test_framework/test_framework.py) arguments parser.
Tested ACK 2198f79e87b3a8bfcda59e51225ab4cb789ccc53