Re: Timeout control within tests

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>

To: Noah Misch <noah@leadboat.com>

Cc: pgsql-hackers@postgresql.org

Date: 2022-02-18T05:48:25Z

Lists: pgsql-hackers

Hi,

On 2022-02-17 21:28:42 -0800, Noah Misch wrote:
> I propose to have environment variable PG_TEST_TIMEOUT_DEFAULT control the
> timeout used in the places that currently hard-code 180s.

Meson's test runner has the concept of a "timeout multiplier" for ways of
running tests. Meson's stuff is about entire tests (i.e. one tap test), so
doesn't apply here, but I wonder if we shouldn't do something similar?  That
way we could adjust different timeouts with one setting, instead of many
different fobs to adjust?

Greetings,

Andres Freund

Commits

Replace PGISOLATIONTIMEOUT with 2 * PG_TEST_TIMEOUT_DEFAULT.
- c99c67fc43f8 16.0 landed
Introduce PG_TEST_TIMEOUT_DEFAULT for TAP suite non-elapsing timeouts.
- f60bb3e0a904 14.3 landed
- 8700a487359f 12.11 landed
- 7f2e1befc039 10.21 landed
- 49e8a5d39981 11.16 landed
- 29ec94efd08b 13.7 landed
- f2698ea02ca8 15.0 landed
Use PG_TEST_TIMEOUT_DEFAULT for pg_regress suite non-elapsing timeouts.
- 766075105c21 15.0 landed
Use annotations to reduce instability of isolation-test results.
- 741d7f1047fe 14.0 cited