Re: [RFC PATCH 3/3] test-lib: add the '--stress' option to run a test repeatedly under load
- From
SZEDER Gábor <szeder.dev@gmail.com>
- Date
- Dec 6, 2018, 22:56 UTC
- Message-ID
- <20181206225601.GO30222@szeder.dev>
- In-Reply-To
- <20181205213625.GD19936@sigill.intra.peff.net>
On Wed, Dec 05, 2018 at 04:36:26PM -0500, Jeff King wrote:
> The signal interrupts the first wait.
Ah, of course. I'm ashamed to say that this is not the first time I forget about that...
Show 8 quoted lines
> > Bash 4.3 or later are strange: I get back the shell prompt immediately > > after ctrl-C as well, so it doesn't appear to be waiting for all > > remaining jobs to finish either, but! I don't get any of the progress > > output from those jobs to mess up my next command. > > Interesting. My bash 4.4 seems to behave the same as dash. It almost > sounds like the SIGINT is getting passed to the subshells for you. > Probably not really worth digging into, though.
The subshell does indeed get SIGINT. I don't know why that happens, to my understanding that should not happen.
Show 17 quoted lines
> In case anybody is playing with this and needed to simulate a stress > failure, here's what I used: > > diff --git a/t/t0000-basic.sh b/t/t0000-basic.sh > index b6566003dd..a370cd9977 100755 > --- a/t/t0000-basic.sh > +++ b/t/t0000-basic.sh > @@ -1171,4 +1171,11 @@ test_expect_success 'very long name in the index handled sanely' ' > test $len = 4098 > ' > > +test_expect_success 'roll those dice' ' > + case "$(openssl rand -base64 1)" in > + z*) > + return 1 > + esac > +'
Wasteful :)
test $(($$ % 42)) -ne 0