Re: [PATCH 2/2] tests: introduce --stress-jobs=<N>
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Mar 3, 2019, 02:30 UTC
- Message-ID
- <CAPig+cTvj0BL1YjKhpmLVqADxRSb+17aO1+fPmOYPF7Bj_TppQ@mail.gmail.com>
- In-Reply-To
- <281d3f1d19d1c93e8d1e66ae16fe3fb286554c0a.1551561582.git.gitgitgadget@gmail.com>
On Sat, Mar 2, 2019 at 4:19 PM Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> wrote:
Show 8 quoted lines
> 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@gmx.de>