• Currently, the cobra message does not describe the formatting or potential arguments for --test-args and -stress-args. I think the following could be specified like:

  • stress-args: additional arguments to pass to stress, prefixed with -. E.g. --stress-args='-maxtime=30s'. See all stress args here https://github.com/cockroachdb/stress/blob/master/main.go
  • test-args : additional arguments to pass to the go test binary, prefixed with -test.{arg}. For example: --test-args='-test.timeout 1s'. Learn about go test args here [??]. (I'm not sure if the msg should point to a CRDB specific list of go test args)

• Currently, the cobra message does not note that the user can pass bazel specific args behind --. Perhaps in the flag list, we could add something like:

  • --: add additional arguments to bazel, prefixed with --, e.g. -- --sandbox_debug. Note: the dev maintainers would like all commonly used bazel args to get passed directly to dev. Please file an issue if you're commonly reaching for the bazel flag!

• Currently, its unclear which flags operate on the dev level or go test level. It could be nice to specify which dev flags are merely shortcuts to go test, (e.g. -verbose)

Jira issue: CRDB-16361

Epic CRDB-15061