
Maybe this is related to the thread [HACKERS] regression failure in CVS
HEAD

I've installed postgresql-7.3.2 on HP-UX yesterday.

When running 'gmake -C regress check'
the process does not return.

File ./src/test/regress/regression.out shows

parallel group (13 tests):  float8 int2 varchar text float4 int8 int4
name oid char boolean bit numeric
     boolean              ... ok
     char                 ... ok
     name                 ... ok
     varchar              ... ok
     text                 ... ok
     int2                 ... ok
     int4                 ... ok
     int8                 ... ok
     oid                  ... ok
     float4               ... ok
     float8               ... ok
     bit                  ... ok
     numeric              ... ok
test strings              ... ok
test numerology           ... ok
parallel group (20 tests):  point lseg

ps (filtered) shows
      ch 16635 16492  0 09:29:13 ttyp2     0:00 gmake check
      ch 16763 16635  0 09:29:23 ttyp2     0:00 gmake -C src/test check
      ch 16764 16763  0 09:29:24 ttyp2     0:00 gmake -C regress check
      ch 16769 16764  0 09:29:24 ttyp2     0:00 /bin/sh ./pg_regress
--temp-install --top-builddir=../../..
      ch 19276 16769  0 09:31:31 ttyp2     0:00 tee ./regression.out
      ch 19274 16769 173 09:31:31 ttyp2    31:45 /bin/sh ./pg_regress
--temp-install --top-builddir=../../..
      ch 19443 19274  1 09:32:56 ttyp2     0:00 <defunct>
      ch 19446 19274  0 09:32:56 ttyp2     0:00 <defunct>

Regards, Christoph



Tue, 11 Mar 2003 10:09:11 +0100
Christoph Haller <ch@rodos.fzk.de>
gmake -C regress check failure
Christoph Haller <ch@rodos.fzk.de> writes:
> I've installed postgresql-7.3.2 on HP-UX yesterday.
> When running 'gmake -C regress check'
> the process does not return.

See doc/FAQ_HPUX:

: The parallel regression test script (gmake check) is known to lock up
: when run under HP's Bourne shells: /usr/bin/sh and /sbin/sh.  This is a
: known defect JAGad84609, the fix for which is not yet in any released
: HP-UX version or shell patches.  To work around it, use ksh to run the
: regression script:
: 	gmake SHELL=/bin/ksh check
: 
: If you see that the tests have stopped making progress and only a shell
: process is consuming CPU, kill the shell process and start over with the
: above command.

			regards, tom lane

Tue, 11 Mar 2003 10:29:59 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: gmake -C regress check failure 