Обсуждение: Errors with run_build.pl - 8.3RC2
Hi All,
I was running the run_Build.pl script that is specific
to Buildfarm and encountered errors. I am listing out
the names of the logfiles and the errors that I have
seen.
Can anyone give me some clarity on these errors?
Even though these errors are existing, at the end the
latest version is getting downloaded and when I do a
regression testing it goes through. Can anyone give me
clarity on why these errors are occuring?
The logfiles with the errors are listed below, these
errors are for the version 8.3RC2:
check.log
==================
pgsql.3235/src/test/regress/log/postmaster.log
===================
LOG: database system was shut down at 2008-01-19
17:13:48 EST
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
ERROR: value too long for type character varying(1)
STATEMENT: INSERT INTO VARCHAR_TBL (f1) VALUES
('cd');
ERROR: value too long for type character(1)
STATEMENT: INSERT INTO CHAR_TBL (f1) VALUES ('cd');
ERROR: invalid input syntax for type boolean: " tru
e "
STATEMENT: SELECT ' tru e '::text::boolean AS
invalid;
ERROR: invalid input syntax for type boolean: ""
config.log
conftest.c: In function `main':
conftest.c:62: error: `not' undeclared (first use in
this function)
conftest.c:62: error: (Each undeclared identifier is
reported only once
conftest.c:62: error: for each function it appears
in.)
conftest.c:62: error: parse error before "big"
contrib-install-check.log
=================
/home/CINU/new_build/HEAD/inst/logfile
===================
LOG: database system was shut down at 2008-01-19
17:16:39 EST
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
NOTICE: database "contrib_regression" does not exist,
skipping
NOTICE: type "gbtreekey4" is not yet defined
DETAIL: Creating a shell type definition.
NOTICE: argument type gbtreekey4 is only a shell
NOTICE: type "gbtreekey8" is not yet defined
DETAIL: Creating a shell type definition.
NOTICE: argument type gbtreekey8 is only a shell
NOTICE: type "gbtreekey16" is not yet defined
DETAIL: Creating a shell type definition.
NOTICE: argument type gbtreekey16 is only a shell
NOTICE: type "gbtreekey32" is not yet defined
DETAIL: Creating a shell type definition.
NOTICE: argument type gbtreekey32 is only a shell
NOTICE: type "gbtreekey_var" is not yet defined
DETAIL: Creating a shell type definition.
NOTICE: argument type gbtreekey_var is only a shell
NOTICE: type "cube" is not yet defined
DETAIL: Creating a shell type definition.
NOTICE: return type cube is only a shell
NOTICE: return type cube is only a shell
NOTICE: argument type cube is only a shell
ERROR: bad cube representation
DETAIL: syntax error at end of input
STATEMENT: SELECT ''::cube AS cube;
ERROR: bad cube representation
DETAIL: syntax error at or near "A"
ecpg-check.log
==================
pgsql.3235/src/interfaces/ecpg/test/log/postmaster.log
===================
LOG: database system was shut down at 2008-01-19
17:18:15 EST
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
NOTICE: CREATE TABLE / PRIMARY KEY will create
implicit index "test_pkey" for table "test"
ERROR: duplicate key value violates unique constraint
"test_pkey"
STATEMENT: insert into test ( i , j ) values ( 7 ,
12 )
ERROR: more than one row returned by a subquery used
as an expression
STATEMENT: select i from test where j = ( select j
from test )
LOG: unexpected EOF on client connection
ERROR: relation "nonexistant" does not exist
STATEMENT: select * from nonexistant
initdb.log
WARNING: enabling "trust" authentication for local
connections
You can change this by editing pg_hba.conf or using
the -A option the
next time you run initdb.
install-check.log
==================
/home/CINU/new_build/HEAD/inst/logfile
==================
LOG: database system was shut down at 2008-01-19
17:15:24 EST
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
NOTICE: database "regression" does not exist,
skipping
ERROR: invalid input syntax for type boolean: " tru
e "
STATEMENT: SELECT ' tru e '::text::boolean AS
invalid;
ERROR: invalid input syntax for type boolean: ""
STATEMENT: SELECT ''::text::boolean AS invalid;
pl-install-check.log
=================
/home/CINU/new_build/HEAD/inst/logfile
===================
LOG: database system was shut down at 2008-01-19
17:16:27 EST
LOG: database system is ready to accept connections
LOG: autovacuum launcher started
NOTICE: database "pl_regression" does not exist,
skipping
ERROR: set-valued function called in context that
cannot accept a set
STATEMENT: SELECT perl_set_int(5);
ERROR: set-valued function called in context that
cannot accept a set
STATEMENT: SELECT perl_set_int(5);
Any suggestions regarding the same is appreciated.
Thanks in Advance
Regards
Cinu Kuriakose.
Get the freedom to save as many mails as you wish. To know how, go to
http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html
cinu wrote: > Hi All, > > I was running the run_Build.pl script that is specific > to Buildfarm and encountered errors. I am listing out > the names of the logfiles and the errors that I have > seen. > Can anyone give me some clarity on these errors? > Even though these errors are existing, at the end the > latest version is getting downloaded and when I do a > regression testing it goes through. Can anyone give me > clarity on why these errors are occuring? > > The logfiles with the errors are listed below, these > errors are for the version 8.3RC2: > > > [snip] > Any suggestions regarding the same is appreciated. > > > Errors in the logfiles are expected. Many of these errors are there by design - the regression tests include many tests for error conditions. For example, look at the corresponding logs for a green run here: http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=dungbeetle&dt=2008-01-21%2012:44:01 If the buildfarm script gets through to the end without complaining, then it succeeded. Please note that in general questions regarding use of the buildfarm client belong on its mailing list, not on the pgsql lists. For more information about the list see here: http://pgfoundry.org/mailman/listinfo/pgbuildfarm-members. cheers andrew
On Tue, Jan 22, 2008 at 11:52:08AM +0000, cinu wrote: > Even though these errors are existing, at the end the > latest version is getting downloaded and when I do a > regression testing it goes through. Can anyone give me Regression tests have to test error handling too, so some errors might exactly be what you should see. > ERROR: duplicate key value violates unique constraint > "test_pkey" > STATEMENT: insert into test ( i , j ) values ( 7 , > 12 ) > ERROR: more than one row returned by a subquery used > as an expression > STATEMENT: select i from test where j = ( select j > from test ) > LOG: unexpected EOF on client connection > ERROR: relation "nonexistant" does not exist > STATEMENT: select * from nonexistant These errors are supposed to be there. Comments in the code even tell you why. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!