From: | Georgios Kokolatos <gkokolatos(at)pm(dot)me> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz> |
Subject: | Re: Adding a TAP test checking data consistency on standby with minRecoveryPoint |
Date: | 2019-03-11 14:35:49 |
Message-ID: | 155231494944.16480.1455920899816850878.pgcf@coridan.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I applied the patch on current master and run the tests, but I am afraid that the newly introduced test failed on installcheck-world:
```t/016_min_consistency.pl ............. # Looks like your test exited with 29 before it could output anything.
t/016_min_consistency.pl ............. Dubious, test returned 29 (wstat 7424, 0x1d00)
Failed 2/2 subtests
Test Summary Report
-------------------
t/016_min_consistency.pl (Wstat: 7424 Tests: 0 Failed: 0)
Non-zero exit status: 29
Parse errors: Bad plan. You planned 2 tests but ran 0.
Files=16, Tests=143, 65 wallclock secs ( 0.04 usr 0.04 sys + 6.53 cusr 5.08 csys = 11.69 CPU)
Result: FAIL```
To be honest, I have not checked closely on the failure, still it is the only test failing which by itself should be worthwhile mentioning.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-03-11 14:46:12 | Re: Oddity with parallel safety test for scan/join target in grouping_planner |
Previous Message | Tom Lane | 2019-03-11 14:29:53 | Re: [Patch] Log10 and hyperbolic functions for SQL:2016 compliance |