Thread: Regression failed Mac OSX

Regression failed Mac OSX

From
Neil Tiffin
Date:
Using current cvs version on Mac OS X 10.0 built with

./configure
make
made check

test horology             ... FAILED

from the regression.diffs file

Is this a problem or not?

Neil Tiffin
Chicago


[localhost:src/test/regress] ntiffin% cat regression.diffs
*** ./expected/horology.out     Sun Dec  3 08:51:11 2000
--- ./results/horology.out      Wed Apr  4 13:31:02 2001
***************
*** 122,128 ****  SELECT time with time zone '01:30' + interval '02:01' AS "03:31:00-08";   03:31:00-08  -------------
!  03:31:00-08  (1 row)
  SELECT time with time zone '01:30-08' - interval '02:01' AS "23:29:00-08";
--- 122,128 ----  SELECT time with time zone '01:30' + interval '02:01' AS "03:31:00-08";   03:31:00-08  -------------
!  03:31:00-07  (1 row)
  SELECT time with time zone '01:30-08' - interval '02:01' AS "23:29:00-08";
***************
*** 140,146 ****  SELECT time with time zone '03:30' + interval '1 month 04:01' AS 
"07:31:00-08";   07:31:00-08  -------------
!  07:31:00-08  (1 row)
  SELECT interval '04:30' - time with time zone '01:02' AS "+03:28";
--- 140,146 ----  SELECT time with time zone '03:30' + interval '1 month 04:01' AS 
"07:31:00-08";   07:31:00-08  -------------
!  07:31:00-07  (1 row)
  SELECT interval '04:30' - time with time zone '01:02' AS "+03:28";

======================================================================



Re: Regression failed Mac OSX

From
Peter Bierman
Date:
At 5:47 PM -0500 4/4/01, Neil Tiffin wrote:
>Using current cvs version on Mac OS X 10.0
>
>test horology             ... FAILED


I can't reproduce this on a 10.0 (4K78) system. I just ran the regression tests from cvs HEAD downloaded @ 16:10 PDT on
aG3/350. It also passed several dozen iterations on a G4/400 and a G4/450x2 running 10.0.1.
 

Looping (make clean; make runcheck) in a shell while loop seems to eat all available disk space, but I don't think
that'sa PG bug.
 

Oooh, while waiting for another check to pass, I read the pgsql-hackers archives, and I see that the horology test
problemwas because of daylight savings time (on all platforms). It appears to have been resolved, because current
sourcesdon't have the problem.
 

-pmb