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 1ta6yH-00GIb7-4B for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 21 Jan 2025 05:38:41 +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 1ta6yF-00BY8T-UZ for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 21 Jan 2025 05:38:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ta6yF-00BY8L-Kp for pgsql-pkg-debian@lists.postgresql.org; Tue, 21 Jan 2025 05:38:39 +0000 Received: from mail-yb1-xb36.google.com ([2607:f8b0:4864:20::b36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ta6yD-000g9W-0g for pgsql-pkg-debian@postgresql.org; Tue, 21 Jan 2025 05:38:38 +0000 Received: by mail-yb1-xb36.google.com with SMTP id 3f1490d57ef6-e46c6547266so7457054276.3 for ; Mon, 20 Jan 2025 21:38:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737437916; x=1738042716; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=VUfp3yTLavJQZK/cZxqVBu8sxOC0qFw54ns4V+huEQA=; b=godMEFnx01PpAbRC3fR5UWQTwNEbymFr9aJ59jULUzetgLIauy+3Pubak8jlm79gvt rUTeSOw3/KyHXJYTzUFcsMEkAEqT56e4gGqP78e8JbntgrAda9SkocMUO5vVFlZTLIr/ zBB856OZs/ffO5UnXMvfOmnPDIls5EyfJR7knEAMyHXspRB6weWjAtlVX714clvjIO4S rtPO1+oYHPo/f2m1nbPwDDlEy5JXIfZT0k2KK4l4KPlNF7yNJ0Q5+3TU54jbtHQCmCIU eNQL2cDCktEYxDTWK/LrcrSVlxuceW8fosDn4QRcMU1RnuXrTgKs9425tsJBsPs4c5bu 3Mfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737437916; x=1738042716; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=VUfp3yTLavJQZK/cZxqVBu8sxOC0qFw54ns4V+huEQA=; b=pS6WwnZHThtN+BnFglLFUpuGvOjCLTTiMIESFIuHKwxYs3r+YUbQuNn5riYQIqBzMx KHMCjok1gmE47TKdmp0oiB0Zue7OgPUUxHtvDTKFWYU8TZCvPsH0+AbhO9RTldSulXo6 +3ClFz+hYUPwb2Oj0LTzT5YbjxVNq/g4lgGW8XuK47alqecz+93l77Bu1ukXMl7jJmVz st71oElmdtzeI0U+zLnmkGJ95ckc3KMfXJmf3dBSHzwqu7JAUz6Bm2oe+BHtJ/awJ85C VEuWzbO+0OwvzPeoxxsLvSUzuX6Rmhtjbogvd9jgz2+JdEGhiSaYIdosTEjN0w8GAmJh a0kw== X-Gm-Message-State: AOJu0YzsS/ZwRzU//75CbJL68shF+faH9GPEi82/WBqHlR1zL5b3r5pz l3gkqONseo78DmcROVOUKAkt/GHhPggss+c1snY8wc08G3iVxdbreft4cCgFK1Atv+r1/XxmcE5 Fa7XkC4ZES+h+7X486bSLyNDJuVA/sS+Y X-Gm-Gg: ASbGncuF7d/xmf+xiPtWHlakqICJQ7L4p+W9C0695KQaTQm2uUvSczhol2wvA5Z1GvS wgKxLyHYHdy6cGEUGjFFCeBoeSnEsCpCiwO+bLjXRPrULcD/uDbRq X-Google-Smtp-Source: AGHT+IFQKYj/WyIaDIkz/RY4JEBF2nFo1IRJHRZ33BhDVUrtUny/7YW3wt0zbM5wOLaT5FZ2nSC9Tnnuv1C+B+WJE+w= X-Received: by 2002:a05:6902:1791:b0:e57:3490:d952 with SMTP id 3f1490d57ef6-e57b105aa9fmr12744168276.19.1737437916568; Mon, 20 Jan 2025 21:38:36 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Brian Cosgrove Date: Mon, 20 Jan 2025 23:38:25 -0600 X-Gm-Features: AbW1kvYkUENnROpF08K2IeWfsaVstcyBb6KNMA5VsqHlhS5TM2aeMQCkYstxz8c Message-ID: Subject: Re: PgBouncer 1.24.0 - New upstream version To: Bradford Boyle Cc: pgsql-pkg-debian@postgresql.org Content-Type: multipart/alternative; boundary="000000000000d62a35062c30c9be" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d62a35062c30c9be Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I think this note in the psycopg 3.2.4 news is what we're seeing in the pgbouncer tests: https://github.com/psycopg/psycopg/compare/3.2.3...3.2.4#diff-87f7a7bb7fe8d= bed76e16b67b87f27bda7b779b56e7d93ed3350d77ee4a3f217R20-R23 On Mon, Jan 20, 2025 at 11:25=E2=80=AFPM Brian Cosgrove wrote: > Yes, please do. A Postgres client package (psycopg) update causing failin= g > integration tests seems highly unlikely to be a genuine issue for the > pgbouncer. > > I also reproduced locally the failures you're seeing on Salsa. I notice > that there are relevant changes in psycopg 3.2.4 and I think that there a= re > some assertions needing updates in the upstream project. > > I'll file an issue with pgbouncer but for now please unblock the upload. > > On Mon, Jan 20, 2025 at 10:42=E2=80=AFPM Bradford Boyle < > bradford.d.boyle@gmail.com> wrote: > >> Hi Brian, >> >> I was looking at the package for pgBouncer 1.24.0 again today and it >> looks like the tests are failing [0]. After reading through the logs, it >> looks like psycopg in testing and unstable was updated to 3.2.4 this >> past Friday. I am able to reproduce the test failures in dev environment >> by updating the version in requirements.txt. Should we disable the main >> test suite for now to unblock the upload of 1.24.0? >> >> Regards, >> >> --Bradford >> >> [0]: https://salsa.debian.org/postgresql/pgbouncer/-/jobs/6962351 >> > > > -- > Brian Cosgrove > --=20 Brian Cosgrove --000000000000d62a35062c30c9be Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think this note in the psycopg 3.2.4 ne= ws is what we're seeing in the pgbouncer tests:=C2=A0https://github.com/psy= copg/psycopg/compare/3.2.3...3.2.4#diff-87f7a7bb7fe8dbed76e16b67b87f27bda7b= 779b56e7d93ed3350d77ee4a3f217R20-R23

On Mon, Jan 20, 2025 at 11:25=E2=80=AFPM Brian Cosgrove <= ;cosgroveb@gmail.com> wrote:<= br>
Yes, please do. A Postgres client package (psycopg) update causing failing= integration tests seems highly unlikely to be a genuine issue for the pgbo= uncer.=C2=A0

I also reproduced locally the failures you&= #39;re seeing on Salsa. I notice that there are relevant changes in psycopg= 3.2.4 and I think that there are some assertions needing updates in the up= stream project.

I'll file an issue with pgboun= cer but for now please unblock the upload.

On Mon, Jan 20, 2025 at 10:= 42=E2=80=AFPM Bradford Boyle <bradford.d.boyle@gmail.com> wrote:
Hi Brian,

I was looking at the package for pgBouncer 1.24.0 again today and it
looks like the tests are failing [0]. After reading through the logs, it looks like psycopg in testing and unstable was updated to 3.2.4 this
past Friday. I am able to reproduce the test failures in dev environment by updating the version in requirements.txt. Should we disable the main
test suite for now to unblock the upload of 1.24.0?

Regards,

--Bradford

[0]: https://salsa.debian.org/postgresql= /pgbouncer/-/jobs/6962351


--
Brian Cosgrove


--
Brian Cosgrove
--000000000000d62a35062c30c9be--