RE: PostgreSQL 7.1 beta3 on Windows 2k
От | JJAR |
---|---|
Тема | RE: PostgreSQL 7.1 beta3 on Windows 2k |
Дата | |
Msg-id | IPECLCJEPIFNIDOABNELGEINCBAA.jjarcore@eresmas.com обсуждение исходный текст |
Ответ на | Re: PostgreSQL 7.1 beta3 on Windows 2k (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: PostgreSQL 7.1 beta3 on Windows 2k
(Tom Lane <tgl@sss.pgh.pa.us>)
RE: PostgreSQL 7.1 beta3 on Windows 2k (Peter Eisentraut <peter_e@gmx.net>) |
Список | pgsql-ports |
Tom, I have downloaded PostgreSQL 7.1 beta4 and I have tried the regression tests with "make check", they run until 13 parallel tests or so ( with 13 does with 16 does not ) when it stops you can make it continue killing some processes with the task manager, but I think this would be the same if something inherently bad were happenning within the process. I have tried "make installcheck" and in the end I get this: ############################################################################ ############################ ok ====================== All 76 tests passed. ====================== make[2]: Leaving directory `/usr/src/postgresql-7.1beta4/src/test/regress' make[1]: Leaving directory `/usr/src/postgresql-7.1beta4/src/test' ############################################################################ ############################ but I have seen the word ERROR before this, so I am wondering why. An example of this: ############################################################################ ############################ ============== running regression test queries ============== test boolean ... ERROR: Bad boolean external representation 'XXX' ok test char ... ok test name ... ok test varchar ... ok test text ... ok test int2 ... ERROR: pg_atoi: error in "34.5": can't parse ".5" ERROR: pg_atoi: error reading "100000": Math result out of range ERROR: pg_atoi: error in "asdf": can't parse "asdf" ok test int4 ... ERROR: pg_atoi: error in "34.5": can't parse ".5" ERROR: pg_atoi: error reading "1000000000000": Math result out of range ERROR: pg_atoi: error in "asdf": can't parse "asdf" ok test int8 ... ok test oid ... ERROR: oidin: error in "asdfasd": can't parse "as dfasd" ERROR: oidin: error in "99asdfasd": can't parse "asdfasd" ok test float4 ... ERROR: Bad float4 input format -- overflow ERROR: Bad float4 input format -- overflow ERROR: Bad float4 input format -- underflow ERROR: Bad float4 input format -- underflow ERROR: float4div: divide by zero error ok test float8 ... ERROR: Bad float8 input format -- overflow ERROR: pow() result is out of range ERROR: can't take log of zero ERROR: can't take log of a negative number ERROR: exp() result is out of range ERROR: float8div: divide by zero error ERROR: Input '10e400' is out of range for float8 ERROR: Input '-10e400' is out of range for float8 ############################################################################ ############################ Could you tell me if this is wrong or not please. Thank you for your time. //Juan -----Mensaje original----- De: Tom Lane [mailto:tgl@sss.pgh.pa.us] Enviado el: martes, 06 de febrero de 2001 2:14 Para: JJAR CC: Jason Tishler; pgsql-ports@postgresql.org Asunto: Re: [PORTS] PostgreSQL 7.1 beta3 on Windows 2k "JJAR" <jjarcore@eresmas.com> writes: > [ parallel regression tests hang up in second parallel group ] > I come to this point and nothing happens. The CPU doesn't work at all ( only > 5% CPU power consumption ) and the hard disk is quiet so the process is > dead. Hmm. You might be looking at a shell bug. There are shells out there that lose track of how many children they have when asked to spawn more than a dozen or so parallel children. For example, I see extremely similar behavior when I try to run 'make check' using the standard /bin/sh shell on HPUX 10.20: it locks up partway through the second set of parallel tests. I have to select SHELL=/bin/ksh instead to get the tests to complete. I'm not sure it's quite the same issue, because HPUX's sh goes to 100% CPU usage after getting confused in this way, but it still seems like a likely explanation. Can you run the non-parallel test (make installcheck) successfully? Also, try splitting the parallel groups in the parallel_schedule file into smaller numbers of tests. regards, tom lane
В списке pgsql-ports по дате отправления: