Re: pg_regress breaks on msys

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_regress breaks on msys
Date: 2006-07-20 14:32:47
Message-ID: 27173.1153405967@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

"Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp> writes:
> This is very strange.!!
> boolean ... ok
> char ... diff command failed with status 1: "diff -w "./expected/char.out"
> "./results/char.out" >"./results/char.diff""
> server stopped

Yes, I believe the problem is that our Windows versions of the
WIFEXITED/WEXITSTATUS macros are wrong. pg_regress is trying to verify
that the diff call didn't fail entirely (eg, diff not there or failed
to read one of the files), but the status code diff is returning for
"files not the same" is confusing it.

Can anyone check into what the result status conventions really are on
Windows? I am tempted to change the macros to just swap the bytes,
but I dunno what that will do to their existing usages to check the
result of pclose() or win32_waitpid().

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2006-07-20 14:44:08 Re: Units in postgresql.conf
Previous Message moises 2006-07-20 12:36:53 Transaction Speed

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-07-20 14:54:44 Re: float8 regression failure (HEAD, cygwin)
Previous Message Katsuhiko Okano 2006-07-20 10:07:50 Re: poor performance with Context Switch Storm at TPC-W.