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

From Andres Freund
Subject Re: Curious buildfarm failures (fwd)
Date
Msg-id 20130116013541.GG3089@awork2.anarazel.de
Whole thread Raw
In response to Re: Curious buildfarm failures (fwd)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2013-01-15 20:32:00 -0500, Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.com> writes:
> > On 2013-01-15 19:56:52 -0500, Tom Lane wrote:
> >> At this point I'm more interested in his report in
> >> <alpine.LRH.2.03.1301152012220.773@ast.cam.ac.uk> about
> >> the Assert at spgdoinsert.c:1222 failing.  That's pretty new code, so
> >> more likely to have a genuine bug, and I wonder if it's related to
> >> the spgist issue in <50EBF992.2000704@qunar.com> ...
> 
> > Yes, it looks more like it could be something real. There are
> > suspicously many other failing tests though (misc, with) that don't seem
> > to be related to the spgist crash.
> 
> Looking again, the pg_regress output appears to indicate two separate
> crashes (one during rangetypes, the other during create_index).  The
> reported Assert trap was in the rangetypes test, but the other one
> could very easily have been from spgist code as well.  I'd tend to
> write off all the other reported diffs as followon damage from the
> crashes, at least without clearer evidence that they weren't.  There are
> very many instances in our regression tests where failure to complete
> one test results in bogus diffs in later ones, because DB objects don't
> exist or don't have the expected contents.

I just checked and its just followup damage.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: string escaping in tutorial/syscat.source
Next
From: Andres Freund
Date:
Subject: Re: Curious buildfarm failures (fwd)