Failed regression tests with 7.0.3 on Windows NT 4.0

Failed regression tests with 7.0.3 on Windows NT 4.0

Post by Christian Ullri » Tue, 05 Dec 2000 14:56:30



--vkogqOf2sHV7VnPd
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Hello!

I've just gotten PostgreSQL 7.0.3 to build and actually run under
WinNT 4.0, and the regression tests show two problems: one probably
minor in horology (I suppose there's a wrong time zone somewhere), and
one probably major in alter_table. I attached the diff output.

I'm not very pleased with having to run PostgreSQL on NT, but these
are the facts I can't change. So, keep up the good work!

Yours,

--
Christian Ullrich                    Registrierter Linux-User #125183

"Sie k?nnen nach R'ed'mond fliegen -- aber Sie werden sterben"

--vkogqOf2sHV7VnPd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="regression.diffs"

*** expected/horology.out       Tue Mar 21 05:59:14 2000
--- results/horology.out        Sun Dec  3 14:06:49 2000
***************
*** 235,243 ****
       | Wed Mar 15 08:14:01 2000 PST | @ 34 years                    | Tue Mar 15 08:14:01 1966 PST
       | Sun Dec 31 17:32:01 2000 PST | @ 34 years                    | Sat Dec 31 17:32:01 1966 PST
       | Mon Jan 01 17:32:01 2001 PST | @ 34 years                    | Sun Jan 01 17:32:01 1967 PST
!      | epoch                        | @ 5 mons 12 hours             | Thu Jul 31 05:00:00 1969 PDT
!      | epoch                        | @ 5 mons                      | Thu Jul 31 17:00:00 1969 PDT
!      | epoch                        | @ 3 mons                      | Tue Sep 30 17:00:00 1969 PDT
       | epoch                        | @ 10 days                     | Sun Dec 21 16:00:00 1969 PST
       | epoch                        | @ 1 day 2 hours 3 mins 4 secs | Tue Dec 30 13:56:56 1969 PST
       | epoch                        | @ 5 hours                     | Wed Dec 31 11:00:00 1969 PST
--- 235,243 ----
       | Wed Mar 15 08:14:01 2000 PST | @ 34 years                    | Tue Mar 15 08:14:01 1966 PST
       | Sun Dec 31 17:32:01 2000 PST | @ 34 years                    | Sat Dec 31 17:32:01 1966 PST
       | Mon Jan 01 17:32:01 2001 PST | @ 34 years                    | Sun Jan 01 17:32:01 1967 PST
!      | epoch                        | @ 5 mons 12 hours             | Thu Jul 31 04:00:00 1969 PST
!      | epoch                        | @ 5 mons                      | Thu Jul 31 16:00:00 1969 PST
!      | epoch                        | @ 3 mons                      | Tue Sep 30 16:00:00 1969 PST
       | epoch                        | @ 10 days                     | Sun Dec 21 16:00:00 1969 PST
       | epoch                        | @ 1 day 2 hours 3 mins 4 secs | Tue Dec 30 13:56:56 1969 PST
       | epoch                        | @ 5 hours                     | Wed Dec 31 11:00:00 1969 PST
***************
*** 1159,1165 ****
      | Sat 01 Jan 17:32:01 2000 PST
      | Sun 31 Dec 17:32:01 2000 PST
      | Mon 01 Jan 17:32:01 2001 PST
!     | Thu 13 Jun 00:00:00 1957 PDT
  (67 rows)

  SELECT '' AS eight, f1 AS european_postgres FROM ABSTIME_TBL;
--- 1159,1165 ----
      | Sat 01 Jan 17:32:01 2000 PST
      | Sun 31 Dec 17:32:01 2000 PST
      | Mon 01 Jan 17:32:01 2001 PST
!     | Thu 13 Jun 00:00:00 1957 PST
  (67 rows)

  SELECT '' AS eight, f1 AS european_postgres FROM ABSTIME_TBL;
***************
*** 1247,1253 ****
      | 2000-01-01 17:32:01-08
      | 2000-12-31 17:32:01-08
      | 2001-01-01 17:32:01-08
!     | 1957-06-13 00:00:00-07
  (67 rows)

  SELECT '' AS eight, f1 AS european_iso FROM ABSTIME_TBL;
--- 1247,1253 ----
      | 2000-01-01 17:32:01-08
      | 2000-12-31 17:32:01-08
      | 2001-01-01 17:32:01-08
!     | 1957-06-13 00:00:00-08
  (67 rows)

  SELECT '' AS eight, f1 AS european_iso FROM ABSTIME_TBL;
***************
*** 1335,1341 ****
      | 01/01/2000 17:32:01.00 PST
      | 31/12/2000 17:32:01.00 PST
      | 01/01/2001 17:32:01.00 PST
!     | 13/06/1957 00:00:00.00 PDT
  (67 rows)

  SELECT '' AS eight, f1 AS european_sql FROM ABSTIME_TBL;
--- 1335,1341 ----
      | 01/01/2000 17:32:01.00 PST
      | 31/12/2000 17:32:01.00 PST
      | 01/01/2001 17:32:01.00 PST
!     | 13/06/1957 00:00:00.00 PST
  (67 rows)

  SELECT '' AS eight, f1 AS european_sql FROM ABSTIME_TBL;

----------------------

*** expected/alter_table.out    Tue Mar 14 23:06:55 2000
--- results/alter_table.out     Sun Dec  3 14:10:54 2000
***************
*** 99,274 ****
  --
  VACUUM ANALYZE tenk1;
  ALTER TABLE tenk1 RENAME TO ten_k;
  -- 20 values, sorted
  SELECT unique1 FROM ten_k WHERE unique1 < 20;
!  unique1
! ---------
!        0
!        1
!        2
!        3
!        4
!        5
!        6
!        7
!        8
!        9
!       10
!       11
!       12
!       13
!       14
!       15
!       16
!       17
!       18
!       19
! (20 rows)
!
  -- 20 values, sorted
  SELECT unique2 FROM ten_k WHERE unique2 < 20;
!  unique2
! ---------
!        0
!        1
!        2
!        3
!        4
!        5
!        6
!        7
!        8
!        9
!       10
!       11
!       12
!       13
!       14
!       15
!       16
!       17
!       18
!       19
! (20 rows)
!
  -- 100 values, sorted
  SELECT hundred FROM ten_k WHERE hundred = 50;
!  hundred
! ---------
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
!       50
! (100 rows)
!
  ALTER TABLE ten_k RENAME TO tenk1;
  -- 5 values, sorted
  SELECT unique1 FROM tenk1 WHERE unique1 < 5;
!  unique1
! ---------
!        0
!        1
!        2
!        3
!        4
! (5 rows)
!
  -- FOREIGN KEY CONSTRAINT adding TEST
  CREATE TABLE tmp2 (a int primary key);
  NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'tmp2_pkey' for table 'tmp2'
--- 99,124 ----
  --
  VACUUM ANALYZE tenk1;
  ALTER TABLE tenk1 RENAME TO ten_k;
+ ERROR:  renamerel: unable to rename tenk1.1 to ten_k.1: error 0
  -- 20 values, sorted
  SELECT unique1 FROM ten_k WHERE unique1 < 20;
! ERROR:  Relation 'ten_k' does not exist
  -- 20 values, sorted
  SELECT unique2 FROM ten_k WHERE unique2 < 20;
! ERROR:  Relation 'ten_k' does not exist
  -- 100 values, sorted
  SELECT hundred FROM ten_k WHERE hundred = 50;
! ERROR:  Relation 'ten_k' does not exist
  ALTER TABLE ten_k RENAME TO tenk1;
+ ERROR:  Relation 'ten_k' does not exist
  -- 5 values, sorted
  SELECT unique1 FROM tenk1 WHERE unique1 < 5;
! NOTICE:  mdopen: couldn't open tenk1: No such file or directory
! NOTICE:  RelationIdBuildRelation: smgropen(tenk1): error 0
! NOTICE:  mdopen: couldn't open tenk1: No such file or directory
! NOTICE:  mdopen: couldn't open tenk1: No such file or directory
! NOTICE:  mdopen: couldn't open tenk1: No such file or directory
! ERROR:  cannot open relation tenk1
  -- FOREIGN KEY CONSTRAINT adding TEST
  CREATE TABLE tmp2 (a int primary key);
  NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'tmp2_pkey' for table 'tmp2'

----------------------

--vkogqOf2sHV7VnPd--

 
 
 

Failed regression tests with 7.0.3 on Windows NT 4.0

Post by Tom La » Wed, 06 Dec 2000 03:16:34



> I've just gotten PostgreSQL 7.0.3 to build and actually run under
> WinNT 4.0, and the regression tests show two problems: one probably
> minor in horology (I suppose there's a wrong time zone somewhere), and
> one probably major in alter_table. I attached the diff output.

The horology discrepancy looks like WinNT doesn't have daylight-savings
info before 1970.  Try adding
        horology/.*-cygwin=horology-no-DST-before-1970
to src/test/regress/resultmap.  (I see this has already been done in
current sources.)

Quote:>   ALTER TABLE tenk1 RENAME TO ten_k;
> + ERROR:  renamerel: unable to rename tenk1.1 to ten_k.1: error 0

Apparently a cygwin bug?  Evidently rename() forgets to set errno on
failure.  renamerel() is expecting to see errno = ENOENT when the file
to be renamed doesn't exist.

This is irrelevant for 7.1, since we don't try to do physical file
renames anymore.  If you can live without ALTER TABLE RENAME for awhile
then you could just put up with it for now.  Otherwise, pester the
cygwin folk to fix rename().

                        regards, tom lane

 
 
 

Failed regression tests with 7.0.3 on Windows NT 4.0

Post by Christian Ullri » Wed, 06 Dec 2000 06:16:54


* Tom Lane wrote on Monday, 2000-12-04:


> > I've just gotten PostgreSQL 7.0.3 to build and actually run under
> > WinNT 4.0, and the regression tests show two problems: one probably
> > minor in horology (I suppose there's a wrong time zone somewhere), and
> > one probably major in alter_table. I attached the diff output.

> The horology discrepancy looks like WinNT doesn't have daylight-savings
> info before 1970.  Try adding
[...]
> Apparently a cygwin bug?  Evidently rename() forgets to set errno on
> failure.  renamerel() is expecting to see errno = ENOENT when the file
> to be renamed doesn't exist.

Thanks a lot!

BTW: You're quite right. cygwin's newlib doesn't seem to bother with errno
all that much in stdio. At first grep, it isn't even mentioned in half
the stdio source files.

--
Christian Ullrich                    Registrierter Linux-User #125183

"Sie k?nnen nach R'ed'mond fliegen -- aber Sie werden sterben"

 
 
 

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. Limiting rows in query

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

4. Backup Kill SQL

5. Windows NT 3.51 Server migration to Windows NT 4.0 Beta 2 and INFORMIX Products

6. Need advice/help with data entry forms

7. CA-SAN MATEO-268288--Q/A Testing-Java-Windows NT-Solaris-Windows NT-JDBC-Perl-Sh

8. Advise on Approach db?

9. plpython fails its regression test

10. regression test failed

11. tsearch - Regression tests fail

12. Failed on regression test

13. failed regression tests