From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Refactor all TAP test suites doing connection checks
Date: Mon, 05 Apr 2021 10:57:22 -0400
Message-ID: <513200.1617634642@sss.pgh.pa.us> (raw)
In-Reply-To: <E1lTDox-0006rF-OV@gemulon.postgresql.org>
References: <E1lTDox-0006rF-OV@gemulon.postgresql.org>
Michael Paquier <michael@paquier.xyz> writes:
> Refactor all TAP test suites doing connection checks
Some of the buildfarm seems not to like this. gaur failed here:
==~_~===-=-===~_~== pgsql.build/src/test/authentication/tmp_check/log/regress_log_001_password ==~_~===-=-===~_~==
...
ok 8 - authentication success for method md5, role md5_role
### Reloading node "primary"
# Running: pg_ctl -D /home/bfarm/bf-data/HEAD/pgsql.build/src/test/authentication/tmp_check/t_001_password_primary_data/pgdata reload
server signaled
ack Broken pipe: write( 11, 'SELECT $$connected with user=scram_role$$' ) at /opt/perl5.8.9/lib/site_perl/5.8.9/IPC/Run/IO.pm line 558
and I think hoverfly's failure is the same thing.
I didn't look at the code, but I bet this is similar to the race
conditions we've seen before where a server process may exit before
the perl test script finishes stuffing a command down the pipe.
regards, tom lane
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-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Refactor all TAP test suites doing connection checks
In-Reply-To: <513200.1617634642@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