Re: Curious buildfarm failures (fwd) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Curious buildfarm failures (fwd)
Date
Msg-id 1105.1358278811@sss.pgh.pa.us
Whole thread Raw
In response to Re: Curious buildfarm failures (fwd)  (Sergey Koposov <koposov@ast.cam.ac.uk>)
Responses Re: Curious buildfarm failures (fwd)
Re: Curious buildfarm failures (fwd)
List pgsql-hackers
Sergey Koposov <koposov@ast.cam.ac.uk> writes:
> And I do see the tblspc file left after the finish of "make check":
>      tmp_check/data/pg_tblspc/16385/PG_9.3_201212081/16384/16387

Interesting.  If the tests are run immediately after initdb, 16387
is the relfilenode assigned to table "foo" in the tablespace regression
test.  But why would only that table be left behind?  There are half
a dozen relations in that tablespace at the point of the DROP CASCADE.

BTW, I just finished trying to reproduce this on an IA64 machine
belonging to Red Hat, without success.  So that seems to eliminate
any possibility of the machine architecture being the trigger issue.
The compiler's still a likely cause though.

Anybody have a similar ICC version (dugong's says it is 10.0 20070809)
to try?  Also, Sergey, can you find a non-dot-zero release to try?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Re: pg_ctl idempotent option
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)