From: | Thomas Fanghaenel <tfanghaenel(at)salesforce(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Christoph Berg <cb(at)df7cb(dot)de>, Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Portability issues in TAP tests |
Date: | 2014-07-21 16:00:10 |
Message-ID: | CAK+WP1xw+XRF8CVNZrvFGLj2hq-M=1iROHHMH3U4sJgBdZgdeA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 21, 2014 at 8:21 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> The tests weren't running for me at all on MacOS X, because I was
> missing some prerequisite. So I installed it, and now they promptly
> fail:
>
> ok 2 - initdb --version
> 1..2
> ok 1 - initdb with invalid option nonzero exit code
> ok 2 - initdb with invalid option prints error message
> # Looks like your test exited with 256 just after 2.
> not ok 3 - initdb options handling
I've had the same issue. The error doesn't seem to come from a failed
test, but from within 'prove' itself. Installing Perl 5.18 via
Homebrew, and setting
PROVE="<path-to-your-cellar>/perl518/5.18.2/prove" at configure time
seems to help avoid this particular problem. So I did not attempt any
further diagnosis of the root cause.
From | Date | Subject | |
---|---|---|---|
Next Message | Fabrízio de Royes Mello | 2014-07-21 16:11:46 | Re: [GSoC2014] Patch ALTER TABLE ... SET LOGGED |
Previous Message | Robert Haas | 2014-07-21 15:38:06 | Re: RLS Design |