| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: The real reason why TAP testing isn't ready for prime time |
| Date: | 2015-07-30 03:17:42 |
| Message-ID: | 32172.1438226262@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> hamster has not complained for a couple of weeks now, and the issue
> was reproducible every 4~6 days:
> http://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=hamster&br=HEAD
> Hence let's consider the issue as resolved.
Nah, I'm afraid not. We are definitely still seeing a lot of unexplained
pg_ctl failures; as a recent example,
http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=axolotl&dt=2015-07-29%2018%3A00%3A19
Now maybe that's not the same thing as hamster's issue, but there's still
something funny going on. That's why I've been bitching about the lack of
debug information. I hope that we can make progress on understanding this
once Andrew pushes out the new buildfarm release (especially since some of
his machines are particularly prone to this type of failure, so I trust
he'll update those critters promptly).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-07-30 04:19:57 | Re: Division by zero in planner.c:grouping_planner() |
| Previous Message | Tom Lane | 2015-07-30 02:58:12 | Re: dblink: add polymorphic functions. |