From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: "David Turner" <dturner@twopensource.com>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: t7063-status-untracked-cache.sh test failure on next
Date: Wed, 21 Oct 2015 20:51:32 +0100 [thread overview]
Message-ID: <5627ECC4.6030304@ramsayjones.plus.com> (raw)
In-Reply-To: <1445449800.8302.12.camel@twopensource.com>
On 21/10/15 18:50, David Turner wrote:
> On Wed, 2015-10-21 at 18:05 +0200, Torsten Bögershausen wrote:
>> On 21.10.15 16:37, Ramsay Jones wrote:
>>> Hi Junio,
>>>
>>> While testing the next branch today, I had a test failure, viz:
>>>
>>> $ tail ntest-out-fail
>>> Test Summary Report
>>> -------------------
>>> t7063-status-untracked-cache.sh (Wstat: 256 Tests: 32 Failed: 22)
>>
>> Does this patch help ?
>> (Recently send & tested by David. I just copy & paste the diff)
>
> My patch fixes one of the tests, but Ramsay has a zillion failures
> (presumably because test 1 fails and most everything else follows from
> that).
>
> That test could fail if your clock were running fast and you had
> 1-second resolution timetamps on your filesystem and you were somewhat
> unlucky.
yep. I've just stopped running the test in a loop after about an hour.
In that time it has executed the test about 130+ times (yeah, I forgot
the count), with no failures. I'm going to give up now and declare that
I was simply unlucky! :-D
ATB,
Ramsay Jones
prev parent reply other threads:[~2015-10-21 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 14:37 t7063-status-untracked-cache.sh test failure on next Ramsay Jones
2015-10-21 16:05 ` Torsten Bögershausen
2015-10-21 16:22 ` Ramsay Jones
2015-10-21 17:50 ` David Turner
2015-10-21 19:51 ` 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=5627ECC4.6030304@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tboegi@web.de \
/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).