Re: pgsql: Fix pattern matching logic for logs in TAP tests of pgbench
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andrew Dunstan <andrew@dunslane.net>,
pgsql-committers@lists.postgresql.org,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-06-27T05:48:25Z
Lists: pgsql-hackers
>> Seem quite unnecessary. We haven't found that to be an issue elsewhere >> in the code where slurp_file is used. And in the present case we know >> the file exists because we got its name from list_files(). > > Agreed. That's an exchange between a hard failure mid-test and a > failure while letting the whole test run. Here, we expect the test to > find the log file all the time, so a hard failure does not sound like > a bad thing to me either. Ok, fine with me! -- Fabien.
Commits
-
Cleanup some code related to pgbench log checks in TAP tests
- c4c9c77e56e7 11.13 landed
- 79c24a0c21c4 12.8 landed
- af2e67b47afe 13.4 landed
- 38ff135d9466 14.0 landed
-
Add more debugging information with log checks in TAP tests of pgbench
- 87b2124dfa07 14.0 landed
-
Fix pattern matching logic for logs in TAP tests of pgbench
- c13585fe9e55 14.0 cited