Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1kUDZY-0004vZ-QB
	for pgsql-hackers@arkaria.postgresql.org; Sun, 18 Oct 2020 18:38:24 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1kUDZX-0001hY-GX
	for pgsql-hackers@arkaria.postgresql.org; Sun, 18 Oct 2020 18:38:23 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1kUDZX-0001hQ-9Z
	for pgsql-hackers@lists.postgresql.org; Sun, 18 Oct 2020 18:38:23 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1kUDZR-0003bE-3Q
	for pgsql-hackers@lists.postgresql.org; Sun, 18 Oct 2020 18:38:22 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 09IIcEY5231519;
	Sun, 18 Oct 2020 14:38:14 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Lakhin <exclusion@gmail.com>
cc: Victor Spirin <v.spirin@postgrespro.ru>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: Sometimes the output to the stdout in Windows disappears
In-reply-to: <6480912b-c0e8-c153-a8b1-0d64b16f9cb9@gmail.com>
References: <ac976d8c-03df-d6b8-025c-15a2de8d9af1@postgrespro.ru>
 <4124040.1598898684@sss.pgh.pa.us>
 <b92a7e09-9a60-d76b-e226-7e191fdc6f34@postgrespro.ru>
 <855416.1600022228@sss.pgh.pa.us>
 <ee02eaa2-03f7-74ea-bbdf-3196e506bae3@gmail.com>
 <4156857.1602865112@sss.pgh.pa.us>
 <b32688da-fafc-bbf6-b786-2dd7d0a4d578@gmail.com>
 <117919.1602949857@sss.pgh.pa.us> <132799.1602960277@sss.pgh.pa.us>
 <fca9beed-4902-d955-a691-96950fa54eaa@gmail.com>
 <229665.1603044291@sss.pgh.pa.us>
 <6480912b-c0e8-c153-a8b1-0d64b16f9cb9@gmail.com>
Comments: In-reply-to Alexander Lakhin <exclusion@gmail.com>
	message dated "Sun, 18 Oct 2020 21:30:01 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <231517.1603046294.1@sss.pgh.pa.us>
Date: Sun, 18 Oct 2020 14:38:14 -0400
Message-ID: <231518.1603046294@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

Alexander Lakhin <exclusion@gmail.com> writes:
> I just wanted to inform that the ECPG-test failures can still persist in
> the buildfarm, unfortunately.

Right, but at least now we can see that there are other issues to
investigate.  Personally I stopped paying any attention to buildfarm
ECPG failures on Windows some time ago, figuring they were all the
mysterious stdout-truncation problem.  With that gone there'll be
less noise and more signal in the buildfarm results.

			regards, tom lane