From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Revert "Secure Unix-domain sockets of "make check" temporary clu |
Date: | 2014-03-29 21:21:11 |
Message-ID: | 53373947.3040103@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 03/29/2014 04:47 PM, Tom Lane wrote:
> Noah Misch <noah(at)leadboat(dot)com> writes:
>> On Sat, Mar 29, 2014 at 09:32:06AM -0400, Tom Lane wrote:
>>> I'm confused. I do not see a single buildfarm failure that appears
>>> attributable to that patch.
>> Here are some:
>> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=reindeer&dt=2014-03-29%2006%3A00%3A03
> Hm, I was expecting that any failures would be in the main or contrib
> checks. I guess ecpg is a couple directory levels further down though.
>
> In this particular example the path is only about 7 characters too long,
> but I suppose trying to shave off a few characters isn't really going
> to be a robust solution.
>
>
Since you have one of the offending buildfarm machines (dromedary) why
not try this: in the build_env section of the config file, add
PG_REGRESS_SOCK_DIR => "/Users/buildfarm/bf-data/$branch/",
If it works I'll have the buildfarm script default that to a slightly better location in the release I'm about to make.
cheers
andrew
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-03-29 21:34:14 | pgsql: Fix dumping of a materialized view that depends on a table's pri |
Previous Message | Tom Lane | 2014-03-29 20:47:34 | Re: pgsql: Revert "Secure Unix-domain sockets of "make check" temporary clu |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2014-03-29 21:38:03 | Re: [RFC] What should we do for reliable WAL archiving? |
Previous Message | Andrew Dunstan | 2014-03-29 21:10:49 | Re: psql \d+ and oid display |