Very Computer

1. Regression tests failing on abstime due to test date being

From: expected/abstime.out

SELECT '' AS six, ABSTIME_TBL.*
   WHERE ABSTIME_TBL.f1 < abstime 'Jun 30, 2001';
 six |              f1
-----+------------------------------
     | Sun Jan 14 03:14:21 1973 PST
     | Mon May 01 00:30:30 1995 PDT
     | epoch
     | current
     | -infinity
     | Sat May 10 23:59:12 1947 PST
(6 rows)

---
In my system current is now after Jun 30 and so doesn't appear. If the test
passes it's actually a huge problem ;).

Is it necessary to pick dates so close in the "future" when setting up the
test? How about setting such dates to some date when the next version is
likely to be out :). Then at least if it fails it's a convenient time to
ask newbies to upgrade to 7.X or even 8.

It's just a very minor issue, but this has happened before - one release
had the testdate < Y2K.

Cheerio,
Link.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://www.postgresql.org/search.mpl

2. Help with table lookup error

3. Another regression test fails to stand the test of time

4. FindFirst does not work ! HELP !!!

5. regression test failed

6. NYC perm;:VB,C,C++,ORACLE UNIX !!!

7. Solaris/Sparc: Regression test fails

8. Dump Devices

9. PostgreSQL regression test fails - why?

10. tsearch - Regression tests fail

11. Solaris/Sparc: Regression test fails

12. [SQL] Regression tests failed on 7.2rc2

13. plpython fails its regression test