From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | libpq URI and regression testing |
Date: | 2012-04-17 13:47:26 |
Message-ID: | 1334669935-sup-1398@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
When I committed Alex Shulgin's patch to add URI support to libpq, I
included the test harness as well. However, due to it being in a
separate subdirectory that did not previously had tests, it's not being
run by buildfarm.
It's not considered in "make installcheck-world" either.
What's the preferred way to make it automatically tested as much as
possible? I know the buildfarm does not run "installcheck-world", so if
we want it there, it'd need a bit more code on the client side. I think
it would be wise to have it also run on installcheck-world.
Hmm. Just had this thought: not all platform support the same socket
types. Maybe we should have separated the .in file in three parts:
IPv4, IPv6, unix-domain socket. That way each platform would only run
tests that pertain to it. Right now there's a single "regress.in" file
that lists all the tests.
Opinions?
--
Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2012-04-17 13:49:30 | Re: Gsoc2012 idea, tablesample |
Previous Message | Thom Brown | 2012-04-17 13:44:50 | Re: Slow temporary tables when using sync rep |