Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1trKNi-002BsH-Su for pgsql-hackers@arkaria.postgresql.org; Sun, 09 Mar 2025 17:24:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1trKNg-00Akty-FW for pgsql-hackers@arkaria.postgresql.org; Sun, 09 Mar 2025 17:24:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1trKNf-00Aktp-Tq for pgsql-hackers@lists.postgresql.org; Sun, 09 Mar 2025 17:24:04 +0000 Received: from mail-pl1-x633.google.com ([2607:f8b0:4864:20::633]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1trKNb-001ssx-2p for pgsql-hackers@postgresql.org; Sun, 09 Mar 2025 17:24:03 +0000 Received: by mail-pl1-x633.google.com with SMTP id d9443c01a7336-224341bbc1dso30419745ad.3 for ; Sun, 09 Mar 2025 10:24:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1741541038; x=1742145838; darn=postgresql.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=Ato3hddBuoZ6nB1f0y330ZUokNFYJ1eI1CJ6pnRqaLs=; b=VKsMcoU45/y9YBxwpow0+qOEqoiPbEPzUtPSUeZ3jezeXHByychjmDrYK1ftadDBbO QJs1cluQVqn67L3Ow3D01llVOGJB/6gM83WatuKdrTs5tugsIbenMmNEy0OAkNSNyMXD GOs7zvaNSRfSq5v/Rg+8PO/XBu7dF87GDLF+Q= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741541038; x=1742145838; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Ato3hddBuoZ6nB1f0y330ZUokNFYJ1eI1CJ6pnRqaLs=; b=kSIGnPN+7eHJglscUwzOKk9LVjRyawtpSFdeiq7ZtLOZfum+3SxiM0Vr5Ipkcz1IcZ xWXhHhWm1wRO+5xex3QF9wsgJ2gZ1wmVBUOsQO4YjqZgzUZtWGVfXlEtrGkn2h2nCP2t ZwdWGtXeBIhGOVpzDBjWOxH1fnPf5U7XYit6yi6OuHa+fjJnBrqnjSJm5kYpzXh5wkxF 3KKI8RTm3HTPcIui91woBTmi7B9+XysgpsjMA7g+VYaYU3p3wyASeuEvpLd4pfOBi1cW abS9zm64wnPtZ+R2gIQv6TvcHrNHAnU52BcXg0P/2X0s13GwFBtWKOJQVvl5tmKETtxT vdwQ== X-Forwarded-Encrypted: i=1; AJvYcCVwlyu0HtwG1pQ10sQhZjoj+7+A0X5t/2WS/D+bI+GKDUFozCge6Dvx7LVeU8t88Sfem0NVlqYlkyjbSW9v@postgresql.org X-Gm-Message-State: AOJu0YzKZ99g7WT/NLKnG1KhN9qCPLqIhAf953IVKNDQKxgetiSMgc5L 0YNXHeW7AlVagU7P8KhgrV7PAKfCVDWbhKg7MZzJ72vtY+T1S/ms1ElCYaTHNg== X-Gm-Gg: ASbGncu3+uein/zwlKCK2m9nBwmocOPLFbypnu1+z3+NjIapHgBbjuAftG0Ibp5sp2S c5GXqhqa8X4cQ1lgirQoz53JUVpmmrAH1VsNBnxFietNZxW702/T8mMFT/SIlkhuoCijSlOCOLC ZdOLtTeLUFkIpomoTzkWduthXjjF1l5sDPC1f4mOFkgesytlLX5xXJjaKmedJQhy1C6cLTr2D0f bAuZNS5CubooAthMncd2I6jQpgY+sLz/xAR7M/TswnHOt9X08RPi9dZT8MbJHGQ60c7Dv+Rw35p sR0JdXyxMGnk95nWe6ZCtjyE7pSrGmBtFsW2/p8= X-Google-Smtp-Source: AGHT+IH7LjZdZMnTkqu5S7YHorNlPNvTabKLl6BiVikTCfHXmuOR2+48COQrqgQHRzf0bMAK0XF1jA== X-Received: by 2002:a17:903:3d0d:b0:220:c63b:d93c with SMTP id d9443c01a7336-22428bd3821mr214592545ad.44.1741541038334; Sun, 09 Mar 2025 10:23:58 -0700 (PDT) Received: from google.com ([2600:1702:a20:5750::46]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-224109e947fsm62390465ad.60.2025.03.09.10.23.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Mar 2025 10:23:57 -0700 (PDT) Date: Sun, 9 Mar 2025 10:23:55 -0700 From: Noah Misch To: Andres Freund Cc: Tom Lane , pgsql-hackers@postgresql.org Subject: Re: BackgroundPsql swallowing errors on windows Message-ID: <20250309172355.05.nmisch@google.com> References: <20250216184740.55.nmisch@google.com> <20250216223951.a3.nmisch@google.com> <684214.1739747924@sss.pgh.pa.us> <20250216235843.7c.nmisch@google.com> <695158.1739753418@sss.pgh.pa.us> <9D3BCBE0-5DC1-4344-A87E-74F6809F2FF8@anarazel.de> <20250217015236.62.nmisch@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sun, Mar 09, 2025 at 12:47:34PM -0400, Andres Freund wrote: > On 2025-02-16 17:52:36 -0800, Noah Misch wrote: > > On Sun, Feb 16, 2025 at 08:42:50PM -0500, Andres Freund wrote: > > > On February 16, 2025 7:50:18 PM EST, Tom Lane wrote: > > > >Noah Misch writes: > > > >> On Sun, Feb 16, 2025 at 06:18:44PM -0500, Tom Lane wrote: > > > >>> I think that > > > >>> IPC::Run may be screwing up here, because I have seen non-Windows > > > >>> CI failures that look like it didn't read all the stderr output. > > > >>> For example, this pgbench test failure on macOS from [1]: > > > > > > > >> https://github.com/cpan-authors/IPC-Run/commit/2128df3bbcac7e733ac46302c4b1371ffb88fe14 > > > >> fixed that one. > > > > > > > >Ah. Do we know whether that fix has made it into our CI images? > > > >(Or anywhere else, for that matter?) > > > > > > The CI images are regenerated three times a week, but for most OSs, they will only install perl modules via the applicable packaging method, so it'll depend on when they pick up that version. > > > > > > On Windows cpan is used, so it should pick that new version fairly quickly if a release has been made. > > > > > > On macos we can't currently use images, so we just cache all the installed > > > macports packages. The cache is keyed by OS version and list of packages > > > to be installed, with no other forced invalidation right now. So it's hard > > > to predict when a new version of a package will be picked up and it will > > > differ between git repositories. I've been wondering whether the cached > > > macports install should just be regularly generated instead, along the > > > other ci images. > > > > The change is not in a release yet. We could have macos install IPC::Run from > > github, or I could get a release cut so it can make its way to macports. > > It'd be great if we could get a release. Yep. I put the tree in the necessary state, and I contacted the person on 2025-02-17 and again on 2025-03-04. I'm scheduled to follow up again on 2025-03-11. > I guess I can figure out the magic > incantations to install it from git for CI There's no need to build anything, so it suffices to do: git clone https://github.com/cpan-authors/IPC-Run.git export PERL5LIB=$PWD/IPC-Run/lib # (or append, if you already have non-empty PERL5LIB)