Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 8cb9434

Browse files
Fix reported runtime for single tests in pg_regress
Commit 558fff0 got the order of the parameters to test_status_failed mixed up which resulted in the runtime being reported as 0 ms. Fix by changing the order to the correct one. No backpatching is needed since this has not been shipped in a release yet. Discussion: https://postgr.es/m/0134C9EC-5F6B-4EAC-B2D5-BB4249BEBD4D@yesql.se
1 parent 44e977d commit 8cb9434

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/test/regress/pg_regress.c

+2-2
Original file line numberDiff line numberDiff line change
@@ -1891,14 +1891,14 @@ run_single_test(const char *test, test_start_function startfunc,
18911891

18921892
if (exit_status != 0)
18931893
{
1894-
test_status_failed(test, false, INSTR_TIME_GET_MILLISEC(stoptime));
1894+
test_status_failed(test, INSTR_TIME_GET_MILLISEC(stoptime), false);
18951895
log_child_failure(exit_status);
18961896
}
18971897
else
18981898
{
18991899
if (differ)
19001900
{
1901-
test_status_failed(test, false, INSTR_TIME_GET_MILLISEC(stoptime));
1901+
test_status_failed(test, INSTR_TIME_GET_MILLISEC(stoptime), false);
19021902
}
19031903
else
19041904
{

0 commit comments

Comments
 (0)