| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christian Ullrich <chris(at)chrullrich(dot)net> |
| Cc: | pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Provide for testing on python3 modules when under MSVC |
| Date: | 2018-05-05 01:45:17 |
| Message-ID: | CAA8=A7_6H_G-4zR1DMm1uJ-VcQR4v=fwh6JrwdiGfxj4KV3vsg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Fri, May 4, 2018 at 7:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Provide for testing on python3 modules when under MSVC
>
> The MSVC critters in the buildfarm seem not to like this.
>
It appears that the three failing critters (whelk, thrips and
woodlouse) are misconfigured, in that they don't have the Python
directory in their PATH setting, so of course plpython3u won't load,
as it won't be able to locate the Python DLL. This hasn't mattered up
to now as they haven't been doing any testing, but it's exposed by our
enabling testing.
On its latest run dory, which also builds with Python3, has passed all
the python tests, so it doesn't (yet) appear that there is anything
wrong with the patch.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Ullrich | 2018-05-05 04:12:15 | RE: pgsql: Provide for testing on python3 modules when under MSVC |
| Previous Message | Andrew Dunstan | 2018-05-04 23:27:28 | Re: pgsql: Provide for testing on python3 modules when under MSVC |