From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: "make installcheck" fails in src/test/recovery |
Date: | 2019-04-19 00:27:07 |
Message-ID: | 20190419002707.GB2660@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 18, 2019 at 01:45:45AM -0400, Tom Lane wrote:
> Is this extra dependency actually essential? I'm not really
> happy about increasing the number of moving parts in this test.
Hmmm. I don't actually object to removing the part depending on
pageinspect in the tests. Relying on the on-disk page format has
proved to be more reliable for the buildfarm than I initially
thought, and we are actually able to keep the same coverage without
the dependency on pageinspect.
Now, I don't think that this is not a problem only for
src/test/recovery/ but to any path using EXTRA_INSTALL. For example,
if you take contrib/ltree_plpython/, then issue "make install" from
this path followed by an installcheck, then the tests complain about
ltree missing from the installation. For the recovery tests, we
already require test_decoding so I would expect the problem to get
worse with the time as we should not restrict the dependencies with
other modules if they make sense for some TAP tests.
I am wondering if it would be better to just install automatically all
the paths listed in EXTRA_INSTALL when invoking installcheck. We
enforce the target in src/test/recovery/Makefile, still we could use
this opportunity to mark it with TAP_TESTS=1.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-04-19 00:30:20 | Comments for lossy ORDER BY are lacking |
Previous Message | Michael Paquier | 2019-04-19 00:08:38 | Re: Adding a TAP test checking data consistency on standby with minRecoveryPoint |