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 ) id 1prh6K-0007dW-Fh for pgsql-hackers@arkaria.postgresql.org; Wed, 26 Apr 2023 15:30:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1prh6I-0004OB-K1 for pgsql-hackers@arkaria.postgresql.org; Wed, 26 Apr 2023 15:30:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1prh6I-0004O1-6W for pgsql-hackers@lists.postgresql.org; Wed, 26 Apr 2023 15:30:34 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1prh6B-00215h-6q for pgsql-hackers@lists.postgresql.org; Wed, 26 Apr 2023 15:30:32 +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 33QFUMnk863240; Wed, 26 Apr 2023 11:30:22 -0400 From: Tom Lane To: Andrew Dunstan cc: Andres Freund , pgsql-hackers@lists.postgresql.org Subject: Re: issue with meson builds on msys2 In-reply-to: <365f59bd-1aaf-0af0-46ee-89e6a0dae391@dunslane.net> References: <08dd6053-deee-52e9-954b-eb69232905c9@dunslane.net> <2506819.1681761221@sss.pgh.pa.us> <7d7dcc20-ba19-5340-9be8-f255e8b42edc@dunslane.net> <20230420150652.jciazjap223iznjp@awork3.anarazel.de> <5bddd941-9819-6655-7a71-3f346050583e@dunslane.net> <6efeb45a-07f9-2291-c8f8-9fb4abbb6ebc@dunslane.net> <848511.1682519554@sss.pgh.pa.us> <851356.1682521091@sss.pgh.pa.us> <365f59bd-1aaf-0af0-46ee-89e6a0dae391@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Wed, 26 Apr 2023 11:11:33 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <863238.1682523022.1@sss.pgh.pa.us> Date: Wed, 26 Apr 2023 11:30:22 -0400 Message-ID: <863239.1682523022@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan writes: > If I redirect the output to a file (which is what the buildfarm client > actually does), it seems like it completes successfully, but I still get > a non-zero exit: > pgrunner@EC2AMAZ-GCB871B UCRT64 ~/bf > $ /usr/bin/perl -e 'chdir "root/HEAD/instkeep.2023-04-25_11-09-41"; > system("bin/pg_ctl -D data-C -l logfile stop > stoplog 2>&1") ; print > "BANG\n" if $?; ' > BANG > pgrunner@EC2AMAZ-GCB871B UCRT64 ~/bf > $ cat root/HEAD/instkeep.2023-04-25_11-09-41/stoplog > waiting for server to shut down.... done > server stopped Thats ... just wacko. do_stop() emits "waiting for server to shut down...", "done", and "server stopped" in the same way (via print_msg). How is it that all three messages show up in one context but not the other? Could wait_for_postmaster_stop or get_pgpid be bollixing the stdout channel somehow? Try redirecting stdout and stderr separately to see if that proves anything. > It seems more than odd that we get to where the "server stopped" massage > is printed but we get a failure. Indeed, that's even weirder. do_stop() returns directly to the exit(0) in main(). regards, tom lane