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 1ta6lu-00GGVm-NH for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 21 Jan 2025 05:25:55 +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 1ta6ls-00BS5t-0D for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 21 Jan 2025 05:25:52 +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 1ta6lr-00BS5l-Nz for pgsql-pkg-debian@lists.postgresql.org; Tue, 21 Jan 2025 05:25:51 +0000 Received: from mail-yb1-xb2b.google.com ([2607:f8b0:4864:20::b2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ta6lp-000fwY-1A for pgsql-pkg-debian@postgresql.org; Tue, 21 Jan 2025 05:25:50 +0000 Received: by mail-yb1-xb2b.google.com with SMTP id 3f1490d57ef6-e5447fae695so8725023276.2 for ; Mon, 20 Jan 2025 21:25:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737437149; x=1738041949; 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=QzrLBnmo96LoK1j0NOoTI5c7xea9eMFCb0m63Uxsbhk=; b=fNMiJbCoswqNxRhw/sOjdMEwVKH2ABkiUmRXhyHTJcN8vJ33YePya1Io4s/58evlHv YNfYJf5E2T5lLXa2u/MaLaVCAiVKAnvs5tAgM3UJEo8m8q2cQ1ytarc98WyvWzrJtogE dOInkCshSAtW3pghVRMFiU75FcbDn/kIawHN32nb5SzRJg6Ii2DyYGfgianePOZWLsE7 ZMv72JKxFpCJTg/TiBWizkzbJJ9nyhwtL1K58MJzSlGILsX8btnbk91RmIUuDuXgPeIE zaBFTPr6oc1sZsZeDBSYx70ZHAU5zHr0fkP3vh0LBkusyvZoic4oW7+EV5+yEva3kx6b LztA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737437149; x=1738041949; 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=QzrLBnmo96LoK1j0NOoTI5c7xea9eMFCb0m63Uxsbhk=; b=e4dCTqmtXH9a55m19O1fWtUbfml5gg0qDdXdv8BGbW6BuXkaG6w7qsMe+7rLSwBSos NR9zk3F+VAsIGMs/giOlNzmFGb5oxXA6F/SDuTJxGP7p4gBQCJXPmfHrm9eTLW39cVvU UWA1tZGgQJItINs/ojG6/9rMWppu5lU1ucsJWHuVjlXH59frhwWlZm711jppbMPDlUPS 8GrErqFOkpWmIdV9nzMM39hfXFVOcMXGKNPBE3rDhKP5W5OjNmtN34bHTVpOOw01/5L+ 5bhU2XEsZ9Ym9Chw29lrZcH0oWdwi5ROfk+qcLR1IWv57Ot0VpeVVV3D2ZJ2i0syGxIC Y5AQ== X-Gm-Message-State: AOJu0Yyci2DlKM5rkomcx+ynbj4w66YINSzvDYYpFR5kfQHae74krJRf ZtwGr8jEGJwelObfERx3rCuizOEFK0F9ZPPn1Y6Wh7bBd2hbLuxgwJJwrUjhHZAkoQaljiUSiZX DzxExuMMZ9tQzdAtPjhqcs/RtChg= X-Gm-Gg: ASbGncuxT7xPcbVFmMdPZmq4YfVs/qqg8bK1sFdMF7OgXc1I31fce7KckSeDoIs+RGh ILtk8tuRUxgqTlPjW7i33xpEHgonoFtY7aLudbZdIHfk9nFXZ10p1 X-Google-Smtp-Source: AGHT+IF0M/FGlLKw6WYs5UcZ7UFH4LTjR7/MFbfz5zoyAg/0wek+/nLI6Kwr5tEyOekgoLSh7w0no764h/NqLRXYEUw= X-Received: by 2002:a05:6902:e0f:b0:e58:7aa:7de4 with SMTP id 3f1490d57ef6-e5807aa82b6mr104572276.45.1737437148891; Mon, 20 Jan 2025 21:25:48 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Brian Cosgrove Date: Mon, 20 Jan 2025 23:25:37 -0600 X-Gm-Features: AbW1kva1_foNjvw4vqHlPV7qE54jT0ITcoA7Wl_AkbzDt7B02KeroWSF5VsbYW8 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="000000000000145553062c309ca5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000145553062c309ca5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yes, please do. A Postgres client package (psycopg) update causing failing 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 are 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 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 > --=20 Brian Cosgrove --000000000000145553062c309ca5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, please do. A Postgres client package (psycopg) update= causing failing integration tests seems highly unlikely to be a genuine is= sue for the pgbouncer.=C2=A0

I also reproduced locally t= he failures you're seeing on Salsa. I notice that there are relevant ch= anges in psycopg 3.2.4 and I think that there are some assertions needing u= pdates in the upstream project.

I'll file an i= ssue with pgbouncer but for now please unblock the upload.

<= div class=3D"gmail_quote gmail_quote_container">
On Mon, Jan 20, 2025 at 10:42=E2=80=AFPM Bradford Boyle <bradford.d.boyle@gmail.com>= ; wrote:
Hi Bria= n,

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
--000000000000145553062c309ca5--