From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Problems with Windows, Was: What's cooking in git.git (May 2013, #01; Fri, 3)
Date: Tue, 07 May 2013 16:27:20 +0200 [thread overview]
Message-ID: <51890F48.3090409@web.de> (raw)
In-Reply-To: <7vvc6zwta7.fsf@alter.siamese.dyndns.org>
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
next prev parent reply other threads:[~2013-05-07 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 23:14 What's cooking in git.git (May 2013, #01; Fri, 3) Junio C Hamano
2013-05-07 14:27 ` Torsten Bögershausen [this message]
2013-05-08 0:30 ` Problems with Windows, Was: " Mark Levedahl
2013-05-08 15:01 ` Torsten Bögershausen
2013-05-09 17:18 ` Ramsay Jones
2013-05-14 19:37 ` Torsten Bögershausen
2013-05-14 22:41 ` Philip Oakley
2013-05-15 6:19 ` Tay Ray Chuan
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=51890F48.3090409@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).