Build farm failure - Mailing list pgsql-hackers

From Gregory Stark
Subject Build farm failure
Date
Msg-id 87myv271j5.fsf@oxford.xeocode.com
Whole thread Raw
Responses Re: Build farm failure
Re: Build farm failure
Re: Build farm failure
List pgsql-hackers
dugong (icc on ia64) has been failing the contrib installcheck consistently
since 6 days ago with errors like:

ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory

I checked a cvs diff between the two timestamps and that's precisely when the
self-adjusting bgwriter changes went in which knocked around bgwriter's
checkpoint logic quite a bit so it seems likely this is a real bug.

On the other hand it seems weird that it only occurs in contrib's check and
not the normal tests. And it also seems weird it only happens on icc ia64 and
not any other architecture under the sun. I installed icc on my machine (ia32)
but didn't get the same problem (we don't seem to have a recent icc ia32 build
farm member).

The only things I know about icc are that it likes to pad structs
unnecessarily and is picky about its -f arguments...


LOG:  database system was shut down at 2007-10-02 02:21:38 MSD
LOG:  autovacuum launcher started
LOG:  database system is ready to accept connections
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
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0
NOTICE:  database "contrib_regression" does not exist, skipping
ERROR:  could not fsync segment 0 of relation 1663/40960/41403: No such file or directory
ERROR:  checkpoint request failed
HINT:  Consult recent messages in the server log for details.
STATEMENT:  CREATE DATABASE "contrib_regression" TEMPLATE=template0


--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Use BIO functions to avoid passing FILE * pointers to OpenSSL
Next
From: Gregory Stark
Date:
Subject: Re: Build farm failure