installcheck-world failure

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: installcheck-world failure
Date: 2010-09-02 17:18:23
Message-ID: 4C7F960F0200002500035047@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I just started trying out the new make targets with "world" in the name.
`make world` and `make install-world` seem to work (unless I'm missing
something), but `make installcheck-world` ends with "Error 2". The
relevant bits seem to be:

make[2]: Entering directory
`/home/kgrittn/git/postgresql/kgrittn/contrib/dblink'
make -C ../../src/test/regress pg_regress

make[3]: Entering directory
`/home/kgrittn/git/postgresql/kgrittn/src/test/regress'
make[3]: `pg_regress' is up to date.

make[3]: Leaving directory
`/home/kgrittn/git/postgresql/kgrittn/src/test/regress'
../../src/test/regress/pg_regress --inputdir=.
--psqldir=/usr/local/pgsql-serializable/bin --dbname=contrib_regression
dblink
(using postmaster on Unix socket, default port)

============== dropping database "contrib_regression" ==============

DROP DATABASE

============== creating database "contrib_regression" ==============

CREATE DATABASE

ALTER DATABASE

============== running regression test queries ==============

test dblink ... FAILED

======================
1 of 1 tests failed.
======================

The differences that caused some tests to fail can be viewed in the
file
"/home/kgrittn/git/postgresql/kgrittn/contrib/dblink/regression.diffs".
A copy of the test summary that you see
above is saved in the file
"/home/kgrittn/git/postgresql/kgrittn/contrib/dblink/regression.out".

make[2]: *** [installcheck] Error 1
make[2]: Leaving directory
`/home/kgrittn/git/postgresql/kgrittn/contrib/dblink'

***
/home/kgrittn/git/postgresql/kgrittn/contrib/dblink/expected/dblink.out
2010-06-16 08:47:55.000000000 -0500
---
/home/kgrittn/git/postgresql/kgrittn/contrib/dblink/results/dblink.out
2010-09-02 11:51:11.000000000 -0500
***************
*** 905,926 ****
ADD COLUMN col4 INT NOT NULL DEFAULT 42;
SELECT dblink_build_sql_insert('test_dropped', '2', 1,
ARRAY['1'::TEXT], ARRAY['2'::TEXT]);
! dblink_build_sql_insert
!
---------------------------------------------------------------------------
! INSERT INTO test_dropped(id,col2b,col3,col4)
VALUES('2','113','foo','42')
! (1 row)
!
SELECT dblink_build_sql_update('test_dropped', '2', 1,
ARRAY['1'::TEXT], ARRAY['2'::TEXT]);
! dblink_build_sql_update
!
-------------------------------------------------------------------------------------------
! UPDATE test_dropped SET id = '2', col2b = '113', col3 = 'foo', col4
= '42' WHERE id = '2'
! (1 row)
!
SELECT dblink_build_sql_delete('test_dropped', '2', 1,
ARRAY['2'::TEXT]);
! dblink_build_sql_delete
! -----------------------------------------
! DELETE FROM test_dropped WHERE id = '2'
(1 row)

--- 905,918 ----
ADD COLUMN col4 INT NOT NULL DEFAULT 42;
SELECT dblink_build_sql_insert('test_dropped', '2', 1,
ARRAY['1'::TEXT], ARRAY['2'::TEXT]);
! ERROR: source row not found
SELECT dblink_build_sql_update('test_dropped', '2', 1,
ARRAY['1'::TEXT], ARRAY['2'::TEXT]);
! ERROR: source row not found
SELECT dblink_build_sql_delete('test_dropped', '2', 1,
ARRAY['2'::TEXT]);
! dblink_build_sql_delete
! --------------------------------------------
! DELETE FROM test_dropped WHERE col2b = '2'
(1 row)

======================================================================

Suggestions?

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-09-02 17:28:44 Re: installcheck-world failure
Previous Message Joshua Tolley 2010-09-02 17:17:39 Re: Synchronous replication - patch status inquiry