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: Michael Paquier <michael@paquier.xyz>,
pgsql-committers@lists.postgresql.org
Date: 2021-06-25T01:36:53Z
Lists: pgsql-hackers
On 6/24/21 8:26 PM, Michael Paquier wrote: > (Forgot to add Andrew in CC, now done) > > On Fri, Jun 25, 2021 at 08:51:19AM +0900, Michael Paquier wrote: >> Andrew, what's the format of the per-thread logs generated on this >> host when running the commands? I'd bet that the checks for the >> client IDs are right, but that some parts of the regex are too picky >> when it comes to this host. > I have tested that on my own Windows host using MSVC and Active Perl, > and those tests pass. I am not sure what's happening here. A simple > way to figure out what's going on would be to make the tests more > talkative and show up the logs that don't match. That's not really an equivalent test. I'm taking a look 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