X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; q=dns; s=default; b=I8nH/6mMWhiY+motsvLV
	YgWSquGyWxYXkUnCVfh/Bh/ChRG6WawwRdKr3zWAPJR2498XamlPKZdsO7ODqSZL
	moSjSNk3YTKgAReydVXwcBT21e29Wumz4tfu9pWfOdtt496rTEPu8TumjLnTd3Uq
	yFbqSY3Zf/9x1dpp0q6OGeQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:date:from:to:subject:in-reply-to
	:references:message-id; s=default; bh=YCwNvXXwzCf1hJ7zJrnCx337IS
	o=; b=PcWxwtWewBEMFfgybUnCwPz+PY0NKShYRNZWzUHywIPOfU5SY+JtKuKtkH
	BWb0uUy7UE0Mz1RIp8uqy3e8e/ltWkv/hjgEBFjccCwUTU5ID5Jsno48F1GYNkRD
	ARUD3q3zivKYhyk5d/jjXvPgT96aFX9ctw8qKOogLt/QRRByY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-4.7 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,KAM_ASCII_DIVIDERS,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=agents, trouble, automation, experiments
X-HELO: tha.dds.dk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 06 Aug 2018 12:30:48 +0200
From: =?UTF-8?Q?Niels_Kristian_=22=C3=86nk=C3=A5=22_Jensen?= <nkj AT internetgruppen DOT dk>
To: cygwin AT cygwin DOT com
Subject: Re: ssh cause mintty terminal not to close (tested on 4 cygwin installations)
In-Reply-To: <1609697605.20180804012442@yandex.ru>
References: <1609697605 DOT 20180804012442 AT yandex DOT ru>
Message-ID: <de3d0fdd7af532be1ba121024f780f7a@internetgruppen.dk>
X-Sender: nkj AT internetgruppen DOT dk
User-Agent: Roundcube Webmail/1.3.0

On 2018-08-04 00:24, Andrey Repin wrote:
> Greetings, Niels Kristian Jensen!
> 
>>>> This may seem like a minor thing, but we have much trouble with
>>>> Jenkins
>>>> builds (started via Cygwin OpenSSH) which randomly hang forever - I
>>>> wonder
>>>>  if this could be a clue in this investigation.
>>> 
>> (cut)
>>> 
>>> Try upgrading your mintty, also, if it's about automated building
>>> environment,
>>> I don't see how's mintty can be involved.
> 
>> If the "non-closure" of mintty  is completely internal in mintty and 
>> not
>> a handshake-mistake with the cygwin dll or the OS, then I agree. It
>> seems to be the case, reading the link provided by Thomas Wolff.
> 
> What I wanted to say is that I don't understand, why do you use mintty 
> in this
> specific case.
> 
> Can you provide a bit more background? Do you use it exclusively to 
> call SSH
> to some remote host?

Hello Andrey,

let's forget about the hanging mintty window. I was chasing a ghost, it 
seems.
Mintty is not involved in the Jenkins automation chain.

I'll write another post where I try to list my trouble and experiments 
with hanging
Jenkins builds invoked via OpenSSH in cygwin on windows slaves/agents.

Best regards,
Niels Kristian Jensen

------------------------------------------
Spejd er sejt!

Det Danske Spejderkorps
------------------------------------------

--
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