From: Ryan Johnson <ryanjohn@ece.cmu.edu>
To: cygwin@cygwin.com
Subject: Re: Mercurial not returning with 20110601 snapshot
Date: Fri, 03 Jun 2011 03:32:00 -0000 [thread overview]
Message-ID: <4DE855B2.6070801@ece.cmu.edu> (raw)
In-Reply-To: <20110603022441.GA31731@ednor.casa.cgf.cx>
On 02/06/2011 10:24 PM, Christopher Faylor wrote:
> On Thu, Jun 02, 2011 at 11:47:47AM -0400, Chris Sutcliffe wrote:
>> On 2 June 2011 09:45, marco atzeri wrote:
>>> On Thu, Jun 2, 2011 at 3:34 PM, Ryan Johnson ?wrote:
>>>> Assuming cygwin sshd is running locally, couldn't you just create an empty
>>>> repo and then try to ssh-clone it?
>>>>
>>>> mkdir ~/test-repo
>>>> cd ~/test-repo
>>>> hg init
>>>> hg clone ssh://localhost/test-repo tr2
>> I tried this and I see the behaviour I described. Adding '--debug' I see:
>>
>> csutclif@bmotec3017201lt:[~/test-repo] $ hg --debug clone
>> ssh://localhost/test-repo tr2
>> running ssh localhost "hg -R test-repo serve --stdio"
>> sending hello command
>> sending between command
>> csutclif@localhost's password:
>> remote: 94
>> remote: capabilities: lookup changegroupsubset branchmap pushkey
>> stream unbundle=HG10GZ,HG10BZ,HG10UN
>> remote: 1
>> sending heads command
>> no changes found
>> checking for updated bookmarks
>> sending listkeys command
>> updating to branch default
>> resolving manifests
>> overwrite False partial False
>> ancestor 000000000000 local 000000000000+ remote 000000000000
>> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
>>
>> It hangs at the last line until I Ctrl-C.
> Thanks for the test case. I can duplicate the problem but, so far, I'm
> stumped. python seems to be hanging in ExitProcess.
It seems that python isn't the problem. I downloaded the snapshot and
tried the test case in strace, and just before hanging it reported:
> 24 26366182 [main] python 10128 pinfo::exit: Calling ExitProcess n
> 0x0, exitcode 0x0
However, hitting ^C caused more output. Additional, similar pairs appear
every minute or two, independent of further ^C (I couldn't actually get
strace to exit until I killed ssh manually):
> 44088209 67106467 [unknown (0x25C4)] ssh 10076 _cygtls::remove: wait 0x0
> 101 67106568 [unknown (0x25C4)] ssh 10076 _cygtls::remove: removed
> 0x2EACE64 element 2
Meanwhile, ps confirms zero python processes and one ssh.
Ryan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-06-03 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 10:44 Chris Sutcliffe
2011-06-02 12:28 ` Christopher Faylor
2011-06-02 13:06 ` Chris Sutcliffe
2011-06-02 13:34 ` Ryan Johnson
2011-06-02 13:46 ` marco atzeri
2011-06-02 15:48 ` Chris Sutcliffe
2011-06-03 2:25 ` Christopher Faylor
2011-06-03 3:32 ` Ryan Johnson [this message]
2011-06-04 1:14 ` Christopher Faylor
2011-06-04 1:57 ` Chris Sutcliffe
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=4DE855B2.6070801@ece.cmu.edu \
--to=ryanjohn@ece.cmu.edu \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).