| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TAP test breakage on MacOS X |
| Date: | 2014-10-07 00:15:31 |
| Message-ID: | 1412640931.30485.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2014-10-02 at 21:18 -0400, Robert Haas wrote:
> > If none of this gets us closer to an answer, I can try to produce a
> > patch that produces more details for such failures.
>
> A test that fails for no reason that can be gleaned from the output is
> not an improvement over not having a test at all.
I understand that this isn't great, and it's certainly something I'm
looking into. But it's like pg_regress saying that psql crashed and
leaving you to find out why. I don't think saying that the entire
regression test suite is useless because of that is fair. The TAP tests
are arguably already much easier to debug than pg_regress ever was.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-10-07 00:33:37 | Re: Promise index tuples for UPSERT |
| Previous Message | Michael Paquier | 2014-10-06 23:50:23 | Re: Failure with make check-world for pgtypeslib/dt_test2 with HEAD on OSX |