database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-16 17:07:43 +03:00
Code Activity

Include pg_test_timing's full output in the TAP test log.

Browse Source 
We were already doing a short (1-second) pg_test_timing run during
check-world and buildfarm runs.  But we weren't doing anything
with the result except for a basic regex-based sanity check.
Collecting that output from buildfarm runs is seeming very
attractive though, because it would help us determine what sort
of timing resolution is available on supported platforms.
It's not very long, so let's just note it verbatim in the TAP log.

Discussion: https://postgr.es/m/3321785.1758728271@sss.pgh.pa.us
This commit is contained in:
Tom Lane
2025-09-24 12:08:55 -04:00
parent 7fcb32ad02
commit 7ccbf6d8b5
1 changed files with 12 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
src/bin/pg_test_timing/t/001_basic.pl
View File

@@ -33,14 +33,23 @@ command_fails_like(
#########################################
# We obviously can't check for specific output, but we can
# do a simple run and make sure it produces something.
# Also, note the output in the log for data collection purposes.
command_like(
[ 'pg_test_timing', '--duration' => '1' ],
my $cmd = [ 'pg_test_timing', '--duration' => '1' ];
my ($stdout, $stderr);
print("# Running: " . join(" ", @{$cmd}) . "\n");
my $result = IPC::Run::run $cmd, '>' => \$stdout, '2>' => \$stderr;
is($result, 1, "pg_test_timing: exit code 0");
is($stderr, '', "pg_test_timing: no stderr");
like(
$stdout,
qr/
\QTesting timing overhead for 1 second.\E.*
\QHistogram of timing durations:\E.*
\QObserved timing durations up to 99.9900%:\E
/sx,
'pg_test_timing: sanity check');
'pg_test_timing: stdout passes sanity check');
note "pg_test_timing results:\n$stdout\n";
done_testing();