Re: [PATCH v2 2/2] tests: introduce --stress-jobs=<N>
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Mar 3, 2019, 15:00 UTC
- Message-ID
- <CAPig+cS1URdnRb0RM0HYQhtmXWn5knx6Ee1Y96Gc9dt_9LmRKA@mail.gmail.com>
- In-Reply-To
- <074628c22b2df82280b06db604196f25300e8f87.1551624293.git.gitgitgadget@gmail.com>
On Sun, Mar 3, 2019 at 9:45 AM Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com> wrote:
Show 13 quoted lines
> [...] > 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. > > Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> > --- > diff --git a/t/README b/t/README > @@ -187,11 +187,10 @@ appropriately before running "make". > variable to "1" or "0", respectively. > > --stress:: > ---stress=<N>::
Shouldn't the "--stress=<N>" line be removed?
Show 7 quoted lines
> Run the test script repeatedly in multiple parallel jobs until > one of them fails. Useful for reproducing rare failures in > flaky tests. The number of parallel jobs is, in order of > - precedence: <N>, or the value of the GIT_TEST_STRESS_LOAD > + precedence: the value of the GIT_TEST_STRESS_LOAD > environment variable, or twice the number of available > processors (as shown by the 'getconf' utility), or 8.