| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ssl tests fail due to TCP port conflict |
| Date: | 2024-06-07 14:25:45 |
| Message-ID: | 1244734.1717770345@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radu Radutiu | 2024-06-07 14:28:18 | Re: Postgresql OOM |
| Previous Message | David E. Wheeler | 2024-06-07 14:23:43 | Re: Patch bug: Fix jsonpath .* on Arrays |