On 2013-05-08 02.30, Mark Levedahl wrote:
> On 05/07/2013 10:27 AM, Torsten Bögershausen wrote:
>> On 2013-05-04 01.14, Junio C Hamano wrote:
>>>   Cygwin portability; both were reviewed by Jonathan, and the tip one
>>>   seems to want a bit further explanation.  Needs positive report
>>>   from Cygwin 1.7 users who have been on 1.7 to make sure it does not
>>>   regress for them.
>> I was trying to verify that cygwin 1.7 is still Ok, but got puzzled.
>> Running the test suite under cygwin doesn't seem to work any more (?):
>> Scenario 1:
>> The PC is running alone, and goes into the screen saver.
>> Pressing CTRL-ALT-DEL didn't get any effect.
>> Scenario 2:
>> The PC didn't react any more, when the test suite was run in background.
>> In 3 or 4 cases the PC needed to be reboot hardly.
>> Using the commits before and after this change makes the test suite hang
>> as well at some point, then it hangs somewhere at TC 3000--4000.
>> Scenario 4:
>> The I disabled the screensaver, upgdated cygwin,
>>   and went back to an older commit:
>> The latest run from commit 52d63e70, April 28,
>> hangs in TC 5500, ok 26 clone shallow object count.
>> I can see 2 times
>> git.exe pull --depth 4 ..A
>> Scenario 5:
>> The run of today 1.8.3-rc1, hangs in t5510,
>> some git.exe are running fetch. (or pull)
>> It seems as if some process/exes are not terminated
>> in the way it should be.
>> I will try on a different machine,
>> comments are wellcome
>> /Torsten
> I have run into very similar problems trying to test these patches, so I 
> declined to reply thinking someone else might have better or at least 
> explicable results. I am able to build git on cygwin 1.7 using the proposed 
> patches, it seems to work, but I've run into strange problems such as the 
> main git repo becoming corrupted, no idea how or why.
> Mark

I tried 1.8.3-rc1 on a different PC, and it seems to have the same hanging.
So I will do some bisecting on master, and try to find out more.

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to