Make data checksum tests more resilient for slow machines The test for re-running checksum enabling was only checking for the data checksum state to transition to 'on', but didn't account for the launcher process having had time to exit, thus getting an error instead of the expected no-op. Adding a pg_stat_activity check for the launcher exiting resolves the error, verified by inducing delay in the launcher.
Also wrap a variable only used in injection point tests within the correct USE macros to avoid warning for an unused variable. All per the buildfarm. Author: Daniel Gustafsson <[email protected]> Reported-by: Buildfarm Discussion: https://postgr.es/m/[email protected] Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/0036232ba8fb282979cff16c8751a361cb85fe76 Modified Files -------------- src/test/modules/test_checksums/t/001_basic.pl | 6 +++++- src/test/modules/test_checksums/test_checksums.c | 2 ++ 2 files changed, 7 insertions(+), 1 deletion(-)
