| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TAP test breakage on MacOS X |
| Date: | 2014-10-30 21:23:11 |
| Message-ID: | 10342.1414704191@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Yup, you read that right, it took 32 seconds to run those dozen utterly
> trivial tests. As far as I could tell by eyeball, pretty much all of the
> time went into test 11, which is odd since it seems not significantly
> different from the others. I think there's something wacky about IPC::Run
> on this platform.
Oh, never mind: after digging into the test source I eventually realized
that there's an initdb happening between tests 10 and 11, and that's
what's eating the time. It might be a thought to print something to
indicate that a time-consuming step is happening; but the lack of any
feedback here isn't exactly IPC::Run's fault.
Anyway, I can confirm Peter's statement that the current tests work even
on quite old platforms, as long as you install IPC::Run.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2014-10-30 21:44:27 | SET TABLESPACE ... NOWAIT |
| Previous Message | Tom Lane | 2014-10-30 21:11:36 | Re: alter user/role CURRENT_USER |