Re: Buildfarm feature request: some way to track/classify failures
От | Gregory Stark |
---|---|
Тема | Re: Buildfarm feature request: some way to track/classify failures |
Дата | |
Msg-id | 87hcshjsfw.fsf@stark.xeocode.com обсуждение исходный текст |
Ответ на | 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
Re: Buildfarm feature request: some way to track/classify failures Re: Buildfarm feature request: some way to track/classify failures |
Список | 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 по дате отправления: