pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org, Nazir Bilal Yavuz <byavuz81@gmail.com>
Subject: Re: pg_upgrade test failure
Date: Mon, 6 Feb 2023 15:43:01 -0800
Message-ID: <20230206234301.33c5vvtd7f3rs6qv@awork3.anarazel.de> (raw)
In-Reply-To: <20230206221422.ykidlne7pmywu4ay@awork3.anarazel.de>
References: <CA+hUKGLfruDhC_8QRGDoCndsdzDVjrf7TYwgsv+OfoAmK2syEg@mail.gmail.com>
	<20230131172806.GM22427@telsasoft.com>
	<CA+hUKGKCVy2=o=d8c2Va6a_3Rpf_KkhUitkWCZ3hzuO2VwLMXA@mail.gmail.com>
	<F0554EC4-4545-4224-B373-9B01EA8D25F1@anarazel.de>
	<CA+hUKG+e788-7YMxFEdScS+V_rVYoM6-H+mTS6caoo8oJBzf=A@mail.gmail.com>
	<CA+hUKGJMynw7BNpsaF3c7hPBEBpzP8T_8WbO-93s=XzcoEsoxw@mail.gmail.com>
	<CA+hUKG+08L=QNq8Zn6xG7f=m41=w=x52YViT6fyRMoCD9RnMzA@mail.gmail.com>
	<3FC7ACA2-5A65-4CAB-AC3D-8F9695A97A2C@anarazel.de>
	<CA+hUKGJnbNm_WmtzmCwPXZpYtqLnMy1=atCHUtNki8pbDhVXSQ@mail.gmail.com>
	<20230206221422.ykidlne7pmywu4ay@awork3.anarazel.de>

On 2023-02-06 14:14:22 -0800, Andres Freund wrote:
> On 2023-02-07 11:03:18 +1300, Thomas Munro wrote:
> > What I see is that there were 1254 FreeBSD tasks run in that window, of
> > which 163 failed, and (more interestingly) 111 of those failures succeeded
> > on every other platform.  And clicking on a few on cfbot's page reveals that
> > it's the new running stuff, and I'm still trying to find the interesting
> > logs...
> 
> I think I figured out why the logs frequently fail to upload - the server is
> still running, so the size changes during the upload, causing the upload to
> fail with errors like:
> 
> [12:46:43.552] Failed to upload artifacts: Put "https://storage.googleapis.com/cirrus-ci-5309429912436736-3271c9/artifacts/postgresql-cfbot/postgres...;: http2: request body larger than specified content length
> 
> I'm testing adding a pg_ctl stop to the on_failure right now.

Pushed the fix doing so.





view thread (35+ messages)  latest in thread

Message-ID: <20230206234301.33c5vvtd7f3rs6qv@awork3.anarazel.de>
Permalink:  ../20230206234301.33c5vvtd7f3rs6qv@awork3.anarazel.de/
Also on:    postgresql.org/message-id/20230206234301.33c5vvtd7f3rs6qv@awork3.anarazel.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: andres@anarazel.de, thomas.munro@gmail.com, pryzby@telsasoft.com, michael@paquier.xyz, byavuz81@gmail.com
  Subject: Re: pg_upgrade test failure
  In-Reply-To: <20230206234301.33c5vvtd7f3rs6qv@awork3.anarazel.de>
  References: <CA+hUKGLfruDhC_8QRGDoCndsdzDVjrf7TYwgsv+OfoAmK2syEg@mail.gmail.com> <20230131172806.GM22427@telsasoft.com> <CA+hUKGKCVy2=o=d8c2Va6a_3Rpf_KkhUitkWCZ3hzuO2VwLMXA@mail.gmail.com> <F0554EC4-4545-4224-B373-9B01EA8D25F1@anarazel.de> <CA+hUKG+e788-7YMxFEdScS+V_rVYoM6-H+mTS6caoo8oJBzf=A@mail.gmail.com> <CA+hUKGJMynw7BNpsaF3c7hPBEBpzP8T_8WbO-93s=XzcoEsoxw@mail.gmail.com> <CA+hUKG+08L=QNq8Zn6xG7f=m41=w=x52YViT6fyRMoCD9RnMzA@mail.gmail.com> <3FC7ACA2-5A65-4CAB-AC3D-8F9695A97A2C@anarazel.de> <CA+hUKGJnbNm_WmtzmCwPXZpYtqLnMy1=atCHUtNki8pbDhVXSQ@mail.gmail.com> <20230206221422.ykidlne7pmywu4ay@awork3.anarazel.de> <20230206234301.33c5vvtd7f3rs6qv@awork3.anarazel.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox