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 1ulB5u-00Bq34-8l for pgsql-hackers@arkaria.postgresql.org; Sun, 10 Aug 2025 18:48:34 +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 1ulB5r-008ICI-0y for pgsql-hackers@arkaria.postgresql.org; Sun, 10 Aug 2025 18:48:31 +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 1ulB5q-008IC9-El for pgsql-hackers@lists.postgresql.org; Sun, 10 Aug 2025 18:48:30 +0000 Received: from mail-pj1-x102e.google.com ([2607:f8b0:4864:20::102e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ulB5n-001pem-0s for pgsql-hackers@postgresql.org; Sun, 10 Aug 2025 18:48:29 +0000 Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-321a2faf29dso384580a91.3 for ; Sun, 10 Aug 2025 11:48:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1754851704; x=1755456504; 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=ywbVuwdMoKPgRi6Q/K1fV/kjfi0G6AfTFAKZZ7JhwRw=; b=QlE9XrRFfneS4B7+Tz8lUts+lUUBz3xKnTLfw3MKePO9OnzIcijnc+eHSEsWnts5gQ Ap/vX4DT7KJerU0e9nxaXvicgqrg+Pxn8STBb7FR9vNqawRx/GaGj2hpEXz1GnvcnP9v 79s5tTKBCS+ponnQHb+Bc4a3I4kYj71lZ/j1A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754851704; x=1755456504; 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=ywbVuwdMoKPgRi6Q/K1fV/kjfi0G6AfTFAKZZ7JhwRw=; b=Bf6U62Awk5CKqVziqnAZPKfr8kDeFCk0vK3iJuN6paGoC8AvK+HEsmkhF8uvO+EN08 1eiPT28643JaceKwNcy6SUEAtiyeUOmh7SXD6BNiG4iqA5UCihQgAW+kZfvyWGjr8hwA /YQ+a1MFACtkZnlOdsFwT5222p3r7UbgOVhRaXctS2IvdTEJc4kNdoYmaigo7p7YWcUH 8lk9GVPqnsjmsqiVR0SmgS0/N7LOvLdA0iRTFi8fg3Ro2KOP5RvLwVNainZnDUAoyaYl iqoxm15lSC66Ebp/IngaZeKj9O3XGlYn1nnkX2zNqSHUaFEhfC16be7J+/9CNWBfTeiC Xieg== X-Forwarded-Encrypted: i=1; AJvYcCVkbgW1L2eKsI8wmo3wI8ebOa0uPDthCVyALHSVqbH8MsOhww7f175KI398MzB5mjk7LUO43sB+4gszFTxw@postgresql.org X-Gm-Message-State: AOJu0YyJs7d7sdh3rooaAXHXUmH8WXW6b+lWbXZnoMDif483Dz0Xgory QENl7DhfgpR1guLTiR1iMvG9H2GbNNkmTrFqFDoynf5byrqLm7nQwgHG90gtJ1ESvQ== X-Gm-Gg: ASbGncunMCpbsa6MDnNGSNhoCU3Em01pxVY99KpRwFTq7yZ8Ft3NTZkRFqIcrqxPqwV CkVZPSMBwxjHm5y+LXUqQJ+hCs4oh+ZKFxjTo2WTQfvnJKpytYgEV8/IZPJroU9SoXwOzMeLynM bl2mL+Wc/vR+W9M3U9kWERuCJ6eWr9Lhg4FIsJd7jjARFz2etOZ5E9pK+3f8FJ8253mTnoGEpFA ulckUWP9GuzeAXJAKkkC8q38k6iSvxSCKIvooqtlGUA5dgFwBUthF5vU4JxtpegU6/bKAdV+K8x TlLaEdK0Mu4ieior8AiusSbgoE5sy80Y0JYd0Ru3cYun/jgLUrmzjAVLQS7lrELTiyg2T8wEd6W uS4m5WBlkDKrktxoQdR+VBHqGmZLEjws7x6lA6X+3PgNXrOWMhdI= X-Google-Smtp-Source: AGHT+IGsmsF9LmR9XP8C13XHLvIQS4Gpc53dUY5YLGs0khpn/oQp4lqFeLzNA2wTa8aW/NUqf89P8g== X-Received: by 2002:a17:90a:d603:b0:321:157a:ee73 with SMTP id 98e67ed59e1d1-321839e75d6mr14344766a91.6.1754851703606; Sun, 10 Aug 2025 11:48:23 -0700 (PDT) Received: from google.com (c-73-15-160-255.hsd1.ca.comcast.net. [73.15.160.255]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-b42890523basm9080509a12.45.2025.08.10.11.48.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 10 Aug 2025 11:48:22 -0700 (PDT) Date: Sun, 10 Aug 2025 11:48:21 -0700 From: Noah Misch To: Andres Freund Cc: Tom Lane , pgsql-hackers@postgresql.org Subject: Re: BackgroundPsql swallowing errors on windows Message-ID: <20250810184821.1a.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> <20250309172355.05.nmisch@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250309172355.05.nmisch@google.com> 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 10:23:55AM -0700, Noah Misch wrote: > 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 [...] https://metacpan.org/dist/IPC-Run is now a fresh release, and https://ports.macports.org/search/?q=ipc-run&name=on shows that version.