pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Alexander Lakhin <exclusion@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: ssl tests fail due to TCP port conflict
Date: Fri, 07 Jun 2024 10:25:45 -0400
Message-ID: <1244734.1717770345@sss.pgh.pa.us> (raw)
In-Reply-To: <da8b76a3-c59c-49c0-8c30-63a85e8ea646@dunslane.net>
References: <d6ee8761-39d1-0033-1afb-d5a57ee056f2@gmail.com>
	<6756fb60-aa5f-442c-90fb-5f29cd1658f0@dunslane.net>
	<be612e1b-ed89-0391-d3f3-657f27336a55@gmail.com>
	<adbe09a3-7782-4ba8-987b-a8498f469a17@dunslane.net>
	<914151.1717623435@sss.pgh.pa.us>
	<CAGECzQSEOPju_27T8GRnBkZp4RG9KH84boUuMdBq-caaZGDamg@mail.gmail.com>
	<da8b76a3-c59c-49c0-8c30-63a85e8ea646@dunslane.net>

Andrew Dunstan <andrew@dunslane.net> writes:
> On 2024-06-06 Th 18:02, Jelte Fennema-Nio wrote:
>> For the PgBouncer test suite we do something similar as the PG its
>> perl tests do, but there we allocate a port between 10200 and 32768:
>> https://github.com/pgbouncer/pgbouncer/blob/master/test/utils.py#L192-L215

> Makes sense to me.

> I still think my patch to force TCP mode for the SSL test makes sense as 
> well.

+1 to both things.  If that doesn't get the failure rate down to an
acceptable level, we can look at the retry idea.

			regards, tom lane





view thread (14+ messages)  latest in thread

Message-ID: <1244734.1717770345@sss.pgh.pa.us>
Permalink:  ../1244734.1717770345@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1244734.1717770345@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andrew@dunslane.net, postgres@jeltef.nl, exclusion@gmail.com
  Subject: Re: ssl tests fail due to TCP port conflict
  In-Reply-To: <1244734.1717770345@sss.pgh.pa.us>

* 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