Increasing timeout of poll_query_until for TAP tests
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2016-07-25T04:22:35Z
Lists: pgsql-hackers
Attachments
- fix-recovery-tap-failures.patch (invalid/octet-stream) patch
Hi all, Lately hamster is failing every 4/5 days on the recovery regression tests in 003 covering the recovery targets, with that: # Postmaster PID for node "standby_2" is 20510 # Timed out while waiting for standby to catch up at t/003_recovery_targets.pl line 36. Which means that poll_for_query timed out for the standby to catch up.. Here is an example of test that failed: http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hamster&dt=2016-07-24%2016%3A00%3A07 This buildfarm machine is legendary known for its slowness, and I don't see a better answer to that than increasing the max timeout of poll_query_until to put that back to green. Thoughts? -- Michael
Commits
-
In tests, await an LSN no later than the recovery target.
- f9c1c6099519 9.6.7 landed
- 5f5d73dd1a81 10.2 landed
- 6078770c1a6c 11.0 landed