From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: ssl tests aren't concurrency safe due to get_free_port() |
Date: | 2022-11-23 02:52:22 |
Message-ID: | 926DE9D5-FE9E-420B-9233-56F6BF26CA4C@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Nov 22, 2022, at 8:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> While looking into a weird buildfarm failure ([1]), I noticed this:
>
>> # Checking port 62707
>> Use of uninitialized value $pid in scalar chomp at /mnt/resource/bf/build/grassquit/REL_11_STABLE/pgsql.build/../pgsql/src/test/perl/PostgresNode.pm line 1247.
>> Use of uninitialized value $pid in addition (+) at /mnt/resource/bf/build/grassquit/REL_11_STABLE/pgsql.build/../pgsql/src/test/perl/PostgresNode.pm line 1248.
>
> Yeah, my animals are showing that too.
>
>> Not quite sure how $pid ends up uninitialized, given the code:
>> # see if someone else has or had a reservation of this port
>> my $pid = <$portfile>;
>> chomp $pid;
>> if ($pid +0 > 0)
>
> I guess the <$portfile> might return undef if the file is empty?
>
Probably, will fix in the morning
Cheers
Andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2022-11-23 02:59:52 | Re: [BUG] FailedAssertion in SnapBuildPurgeOlderTxn |
Previous Message | Peter Smith | 2022-11-23 02:44:49 | Re: Logical replication missing information |