From ad4f2c47de440cdd5d58cf9ffea09afa0da04d6c Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Tue, 29 Mar 2022 16:29:49 -0400 Subject: [PATCH] Make PostgreSQL::Test::Cluster::run_log() return a useful value. Curently, some TAP test that directly call the underlying function PostgreSQL::Test::Utils::run_log() care about the return value, but none of those that call it via PostgreSQL::Test::Cluster::run_log() care. However, I'd like to add a test that will care, so adjust this function to return whatever it gets back from the underlying function, just as we do for a number of other functions in this module. Discussion: http://postgr.es/m/CA+Tgmobj6u-nWF-j=FemygUhobhryLxf9h-wJN7W-2rSsseHNA@mail.gmail.com --- src/test/perl/PostgreSQL/Test/Cluster.pm | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/test/perl/PostgreSQL/Test/Cluster.pm b/src/test/perl/PostgreSQL/Test/Cluster.pm index bee6aacf47c..b6e33516110 100644 --- a/src/test/perl/PostgreSQL/Test/Cluster.pm +++ b/src/test/perl/PostgreSQL/Test/Cluster.pm @@ -2502,8 +2502,7 @@ sub run_log local %ENV = $self->_get_env(); - PostgreSQL::Test::Utils::run_log(@_); - return; + return PostgreSQL::Test::Utils::run_log(@_); } =pod