Re: pgsql: Make the pg_rewind regression tests more robust on slow systems.

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Make the pg_rewind regression tests more robust on slow systems.
Date: 2015-04-23 04:38:16
Message-ID: CAB7nPqQwnJ+kskDee_mZE+zGio6X0R_apRJ3e15+VisYMPAU9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Apr 22, 2015 at 8:37 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)iki(dot)fi> wrote:
> Make the pg_rewind regression tests more robust on slow systems.
>
> There were a couple of hard-coded sleeps in the tests: to wait for standby
> to catch up with master, and to wait for promotion with "pg_ctl promote"
> to complete. Instead of a fixed, hard-coded sleep, poll the server with a
> query once a second. This isn't ideal either, and I wish we had a better
> solution for real-world applications too, but this should fix the
> immediate problem.

Just wondering: why not creating a common routine in TestLib.pm that
returns to the caller the output of stdout, stderr and the exit code?
That would be useful for other tests as well, and would help limiting
the dependency of IPC::Run into TestLib.pm.
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2015-04-23 14:11:36 pgsql: Improve speed of make check-world
Previous Message Alvaro Herrera 2015-04-22 19:23:03 pgsql: Use the right type OID after creating a shell type