From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_regress breaks on msys |
Date: | 2006-07-20 02:33:28 |
Message-ID: | 22643.1153362808@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
I wrote:
> I just committed a change to extract the paths via pg_config_paths.h.
> If that doesn't fix it then I guess the next thing is to put in some
> debug printout to show what values are really getting compiled in :-(
Seems that *did* fix it, which opens a whole new set of questions about
how much you can trust msys' make. However, the latest seahorse results
show we still have a bug or two:
oidjoins ... ok
type_sanity ... ok
opr_sanity ... ok
test geometry ... server stopped
diff command failed: "diff -w "./expected/geometry.out" "./results/geometry.out" >"./results/geometry.diff""
make: *** [check] Error 2
What I think happened here is that diff reported a difference and
pg_regress misinterpreted the exit status as being a hard failure.
Can someone check on whether it's possible to tell the difference
between these cases with Windows diff ?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Agent M | 2006-07-20 02:41:10 | Re: Progress bar updates |
Previous Message | Tom Lane | 2006-07-20 02:19:36 | Re: pg_regress breaks on msys |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-07-20 02:57:40 | Re: pg_regress breaks on msys |
Previous Message | Tom Lane | 2006-07-20 02:19:36 | Re: pg_regress breaks on msys |