Skip site navigation (1) Skip section navigation (2)

Re: So, why isn't *every* buildfarm member failing ecpg right now?

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: So, why isn't *every* buildfarm member failing ecpg right now?
Date: 2007-06-04 14:50:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, Jun 04, 2007 at 03:30:07AM -0400, Tom Lane wrote:
> AFAICS, Peter's recent incomplete updating of error message wording
> should have broken every last man jack of 'em.  And yet there's still
> some green to be seen.  I think we are looking at problems in the ecpg
> test scaffolding.  For instance, dragonfly claims a green build, but
> shows this interesting trace:
> ...
> testing connect/test2.pgc                      ... ./pg_regress: bad substitution

Is it possible to find out which line is reporting this error? Looks to
me like some incompatibility on the shell side.

Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

In response to


pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2007-06-04 15:04:26
Subject: Re: Autovacuum launcher doesn't notice death of postmaster immediately
Previous:From: Bruce MomjianDate: 2007-06-04 14:43:27
Subject: Re: Command tags in create/drop scripts

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group