From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH 0/2] test results for v1.7.12-rc0 on cygwin
Date: Tue, 31 Jul 2012 18:38:55 +0100 [thread overview]
Message-ID: <5018182F.5000501@ramsay1.demon.co.uk> (raw)
In-Reply-To: <5014FAE6.7080009@lsrfire.ath.cx>
René Scharfe wrote:
> Am 28.07.2012 20:46, schrieb Ramsay Jones:
>> Unfortunately, I was unable to reproduce the final failure in t7810-grep.sh.
>> I tried, among other things, to provoke a failure thus:
>>
>> $ for i in $(seq 100); do
>> > if ! ./t7810-grep.sh -i -v; then
>> > break;
>> > fi
>> > done
>> $
>>
>> but, apart from chewing on the cpu for about 50 minutes, it didn't result
>> in a failure. :(
>>
>> However, after looking at test 59, it seems to me to be a stale (redundant)
>> test. So, patch #2 removes that test! :-D [I wish I could reproduce the
>> failure because I don't like not knowing why it failed, but ...]
>
> Removing the test makes sense, since it was needed for --ext-grep only,
> is relatively expensive and a bit fragile (by depending on MAXARGS).
Indeed.
> I'm slightly worried about the non-reproducible failure, though.
Yep, me too.
> Perhaps a timing issue is involved and chances are higher if you leave
> out the option -v?
Yes, one of the "among other things" I tried was to drop the -v, but the
end result was the same. Also, since I have "DEFAULT_TEST_TARGET=prove"
in my config.mak, I tried:
$ for i in $(seq 100); do
> if ! prove --exec sh t7810-grep.sh; then
> break;
> fi
> done
$
But again, it didn't provoke a failure (it did run quite a bit faster ...).
I have now run this test file in excess of 600 times without failure in the
last two evenings (taking about 5-6 hours wallclock time).
[I haven't come remotely close to running the test-suite 600 times on
cygwin in the last 6 years ...]
So, I'm out of ideas (and will stop trying to reproduce the failure).
ATB,
Ramsay Jones
prev parent reply other threads:[~2012-07-31 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 18:46 [PATCH 0/2] test results for v1.7.12-rc0 on cygwin Ramsay Jones
2012-07-29 8:57 ` René Scharfe
2012-07-29 20:33 ` Junio C Hamano
2012-07-31 17:38 ` Ramsay Jones [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5018182F.5000501@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rene.scharfe@lsrfire.ath.cx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).