From: Michael J Gruber <git@drmicha.warpmail.net>
Date: Fri, 08 Apr 2011 07:13:01 GMT
Subject: Re: t3306 failure with v1.7.5-rc1
Message-ID: <4D9EB57D.1060402@drmicha.warpmail.net>
In-Reply-To: <4D9EB406.5080302@viscovery.net>

Johannes Sixt venit, vidit, dixit 08.04.2011 09:06:
> Am 4/8/2011 11:03, schrieb Michael J Gruber:
>> I get this stupid test failure in test 3 of t3306. The problem is that a
>> dangling commit does not get pruned away when it should:
>>
>> 3rd
>> test_must_fail: command succeeded: git cat-file -p
>> 5ee1c35e83ea47cd3cc4f8cbee0568915fbbbd29
>> not ok - 4 verify that commits are gone
>>
>> It's a system where make complains about funny clock (I dunno why) but
>> can we make this more robust? The following helps with "sleep 5" but not
>> with "sleep 4". test_tick does not help. What's going on?
> 
> Looking at the time of day of your last emails (it's ~2 hours in the
> future), I'd say something is fishy with your system's clock. Fix that first.

Well, while you're right about that, an offset should not matter for the
test, right?

About my clock: The result of booting a "different" system on that
box... (In this case even a kubuntu using hw clock in tz...). thanks for
pointing it out!

In any case, that test was on a different box with clean checkout and
make clean. I don't think anyone jumped the clock right in between each
of my 20 or so test runs.

Michael