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 1ta7U3-00GOJW-G6 for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 21 Jan 2025 06:11:32 +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 1ta7U2-00BpO8-79 for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 21 Jan 2025 06:11:30 +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 1ta7U1-00BpO0-Tl for pgsql-pkg-debian@lists.postgresql.org; Tue, 21 Jan 2025 06:11:30 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ta7Tz-000gLJ-1D for pgsql-pkg-debian@postgresql.org; Tue, 21 Jan 2025 06:11:28 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-e461015fbd4so7654520276.2 for ; Mon, 20 Jan 2025 22:11:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737439887; x=1738044687; 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=E5f0wCnODkbqiSvIHBoMW8K1EyC+8lcR+nNCSsk4OUk=; b=P1h1rmLk9aA4j4TFCMcs6p8Bdeo9yJT5UlMSelKQWb5lUH9m/JvcsLb5lgUzF/CNIT pGsiOvW/Be8W9L5YBm3OLqLNIwerzB58tAj9m9rkS73IWJ8Dh3vB/QZZMPTK3LoqJR1l tJpF1klZasjdO+5Cb8u7CNmr72r9iM4kH2KtXq3cWyymcgTYv9sJTt0SJB1RmwKNolSv jukqtSTTnGjULQUOahWgS3SFdO5l9Hzmb6xHfgXvOzQFeQaM05vTrzQzBYQXfieWx0fo vZUoBUUwlRKqitJu2aO4e7ECNv3cnkGAVo7rStVUMssiHGcB1RvRB2NwNEB5qJAcV64J kylg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737439887; x=1738044687; 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=E5f0wCnODkbqiSvIHBoMW8K1EyC+8lcR+nNCSsk4OUk=; b=W/TvUtq8ZMojOnTrspm8bH45P5poUFgEFRNRzfi4qnOg4LSIdLaHO/67K5UmM4F6k6 GzGjVaH0sS7rJzRxv0bxXB3jmnxh0qyteCM2vaj0zjT5JeuwkwGqn/tOjsWI21dL6y6N +fq3tFtU3/loq1wcSABrryoyDQxtat/Fu8SK3BBXjF8jOt6ULaoVWjASKTGoyNvsMtSU 1DaZyD4OAE7WnsmmG3iQewUMTNLgapvshHljh4isZ0X3Hp4fI3+4X2iYIm+NeWgvTZwf cgKkDZgOx3QwUa1cSdiCfPjhzgR0dj+mUbCvfLDK3lb5XvjInwTG9iwtlUyanSmCsdXW wFFw== X-Gm-Message-State: AOJu0YxKc9CVbQ8vIj04Pb7ZYRzHuUYrxrZiv7VCQQK+CEEOXDxSMgiG G5OuOKgwx0ZMzcqA1oi+bOdxp2PnrJfVfz9MxQH/LHMzKQ7DpDS0TpHhdqMqRFDTh1s8thm/hvh TA9Am7HmP4bL6yACxhb40yBWgdPs= X-Gm-Gg: ASbGncsci9pnVdoMFdYxJr8Rfs+fBCPuyPJz6mbq/PLP8KCQzAjaXyZFSU3iLOlbL/S M9VQKzmB0GlKmTLG35H0zZoeSIjLYC7T2OpcBYcMX7nBRNcKCZHM0 X-Google-Smtp-Source: AGHT+IEbFDFktL8TbzscxvtRJGfKSS8He7NCLL6z0AjR7GJI3lSlO2UiR8TQBuc6fyxsLHZELZ9PdecVT26xPpLmqIU= X-Received: by 2002:a05:6902:144b:b0:e57:aa0e:9172 with SMTP id 3f1490d57ef6-e57b1374195mr11838287276.47.1737439886866; Mon, 20 Jan 2025 22:11:26 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Brian Cosgrove Date: Tue, 21 Jan 2025 00:11:16 -0600 X-Gm-Features: AbW1kvZacCRmhfxPI7kGwNXYvQqUg5dbIahpfZTQ6epuZr11epqHxaaVX3mkQRA 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="000000000000468694062c313fdc" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000468694062c313fdc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for the heads up, Bradford. https://github.com/pgbouncer/pgbouncer/pull/1250 On Mon, Jan 20, 2025 at 11:55=E2=80=AFPM Brian Cosgrove wrote: > Ah, funny, we (pgbouncer) just started pinning this in requirements.txt > because of this failure: > https://github.com/pgbouncer/pgbouncer/commit/0cf59fadc0671a7363afa510866= 31b87a26893dc > > On Mon, Jan 20, 2025 at 11:38=E2=80=AFPM Brian Cosgrove > wrote: > >> 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-87f7a7bb7f= e8dbed76e16b67b87f27bda7b779b56e7d93ed3350d77ee4a3f217R20-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 >>> failing integration tests seems highly unlikely to be a genuine issue f= or >>> 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 < >>> 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 environme= nt >>>> by updating the version in requirements.txt. Should we disable the mai= n >>>> 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 >> > > > -- > Brian Cosgrove > --=20 Brian Cosgrove --000000000000468694062c313fdc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for the heads up, Bradford.=C2=A0https://github.com/pgbouncer/pgb= ouncer/pull/1250

On Mon, Jan 20, 2025 at 11:55=E2= =80=AFPM Brian Cosgrove <cosgrove= b@gmail.com> wrote:
Ah, funny, we (pgbouncer) just started pinning = this in requirements.txt because of this failure:=C2=A0https://github.com/pgbouncer/pgbouncer/commit/0cf59fa= dc0671a7363afa51086631b87a26893dc

<= div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 20, 2025 at 11:38=E2=80=AF= PM Brian Cosgrove <cosgroveb@gmail.com> wrote:
I think this note = in the psycopg 3.2.4 news is what we're seeing in the pgbouncer tests:= =C2=A0https://github.com/psycopg/psycopg/compare/3.2.3...3.2.= 4#diff-87f7a7bb7fe8dbed76e16b67b87f27bda7b779b56e7d93ed3350d77ee4a3f217R20-= R23


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

I also = reproduced locally the failures you're seeing on Salsa. I notice that t= here 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 uplo= ad.

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


--
Brian Cosgrove


--
Brian Cosgrove
--000000000000468694062c313fdc--