Re: pgsql: Fix pattern matching logic for logs in TAP tests of pgbench
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Fabien COELHO <coelho@cri.ensmp.fr>, Michael Paquier <michael@paquier.xyz>
Cc: pgsql-committers@lists.postgresql.org,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-06-26T15:01:07Z
Lists: pgsql-hackers
On 6/26/21 2:47 AM, Fabien COELHO wrote: > > Hello Andrew & Michaël, > > My 0.02€: > >> There's a whole lot wrong with this code. To start with, why is that >> unchecked eval there. > > Yep. The idea was that other tests would go on being collected eg if > the file is not found, but it should have been checked anyway. > >> And why is it reading in log files on its own instead of using >> TestLib::slurp_file, which, among other things, normalizes line endings? > > Indeed. > > However, if slurp_file fails it raises an exception and aborts the > whole TAP unexpectedly, which is pretty unclean. So I'd suggest to > keep the eval, as attached. I tested it by changing the file name so > that the slurp fails. 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(). cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
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