Re: [PATCH 2/2] tests: introduce --stress-jobs=<N>
- Date: Sat, 2 Mar 2019 21:30:45 -0500
- From: Eric Sunshine <sunshine@xxxxxxxxxxxxxx>
- Subject: Re: [PATCH 2/2] tests: introduce --stress-jobs=<N>
On Sat, Mar 2, 2019 at 4:19 PM Johannes Schindelin via GitGitGadget
> The --stress option currently accepts an argument, but it is confusing
> to at least this user that the argument does not define the maximal
> number of stress iterations, but instead the number of jobs to run in
> parallel per stress iteration.
> Let's introduce a separate option for that, whose name makes it more
> obvious what it is about, and let --stress=<N> error out with a helpful
> suggestion about the two options tha could possibly have been meant.
This new option probably deserves documentation in t/README alongside
existing documentation for --stress and --stress-limit, and the
existing --stress= documentation ought be updated.
> Signed-off-by: Johannes Schindelin <johannes.schindelin@xxxxxx>