From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org, Stephen Boyd <bebarino@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] t1200: fix a timing dependent error
Date: Tue, 24 Nov 2009 17:14:33 -0800 [thread overview]
Message-ID: <7v7htf76di.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20091125080808.6117@nanako3.lavabit.com> (Nanako Shiraishi's message of "Wed\, 25 Nov 2009 08\:08\:08 +0900")
Nanako Shiraishi <nanako3@lavabit.com> writes:
> The fourth test of show-branch in t1200 test was failing but only
> sometimes. It only failed when two commits created in an earlier
> test had different timestamps. When they were created within the
> same second, the actual output matched the expected output.
Ahh, I actually saw this breakage once, suspected it would be something
like that, but didn't have enough energy/time to dig into it myself.
Thanks.
prev parent reply other threads:[~2009-11-25 1:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 23:08 [PATCH] t1200: fix a timing dependent error Nanako Shiraishi
2009-11-25 1:14 ` Junio C Hamano [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=7v7htf76di.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.com \
/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