Re: Buildfarm feature request: some way to track/classify failures - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Buildfarm feature request: some way to track/classify failures
Date
Msg-id 87hcshjsfw.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: Buildfarm feature request: some way to track/classify failures  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Buildfarm feature request: some way to track/classify failures  (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>)
Re: Buildfarm feature request: some way to track/classify failures  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Buildfarm feature request: some way to track/classify failures  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Also, for completeness, the causes I wrote off as not interesting
> (anymore, in some cases):
>
>  missing BYTE_ORDER definition for Solaris                            | 2007-01-10 14:18:23 |     1

What is this BYTE_ORDER macro? Should I be using it instead of the
AC_C_BIGENDIAN test in configure for the packed varlena patch?

>  row-ordering discrepancy in rowtypes test                            | 2007-02-10 03:00:02 |     3

Is this because the test is fixed or unfixable? If not shouldn't the test get
an ORDER BY clause so that it will reliably pass on future versions? 

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


pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Indexam interface proposal
Next
From: Heikki Linnakangas
Date:
Subject: Re: Indexam interface proposal