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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: So, why isn't *every* buildfarm member failing ecpg right now?
Date: 2007-06-04 07:30:07
Message-ID: 6680.1180942207@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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
http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=dragonfly&dt=2007-06-04%20043001&stg=ecpg-check
shows this interesting trace:

============== running regression test queries        ==============
/export/home/pgfarm/gcc/HEAD/pgsql.28740/src/interfaces/ecpg/test/./tmp_check/install//export/home/pgfarm/gcc/HEAD/inst/bin/createuser -R -S -D -q regressuser1
/export/home/pgfarm/gcc/HEAD/pgsql.28740/src/interfaces/ecpg/test/./tmp_check/install//export/home/pgfarm/gcc/HEAD/inst/bin/createuser -R -S -D -q connectuser
/export/home/pgfarm/gcc/HEAD/pgsql.28740/src/interfaces/ecpg/test/./tmp_check/install//export/home/pgfarm/gcc/HEAD/inst/bin/createuser -R -S -D -q connectdb
testing connect/test1.pgc                      ... skipped
testing connect/test2.pgc                      ... ./pg_regress: bad substitution
make[1]: Leaving directory `/export/home/pgfarm/gcc/HEAD/pgsql.28740/src/interfaces/ecpg/test'

which says that (a) we have a scripting bug, and (b) some other layer is
failing to notice the failure.  Which is two separate bugs by my count.

			regards, tom lane

Responses

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2007-06-04 07:37:09
Subject: Re: What is happening on buildfarm member baiji?
Previous:From: Rodrigo SakaiDate: 2007-06-04 04:34:34
Subject: Re: ERROR: index row size

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