BuildFarm status: recent check failures

Michael Glaesemann <grzm@myrealbox.com> writes:

Just a quick heads-up: I'm not sure of the cause, but it looks like
something recent change to HEAD and REL8_0_STABLE is causing check
failures on the buildfarm machines. A brief (and thoroughly naive)
glance at the details shows a horology test failure.

http://developer.postgresql.org/docs/postgres/regress-evaluation.html#AEN22575

regards, tom lane

Why doesn't the regression test set the timezone to GMT instead of PST. I believe the horology test would just work then.

Jim

---------- Original Message -----------
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Glaesemann <grzm@myrealbox.com>
Cc: PostgreSQL-development Hackers <pgsql-hackers@postgresql.org>
Sent: Mon, 04 Apr 2005 02:08:46 -0400
Subject: Re: [HACKERS] BuildFarm status: recent check failures

Michael Glaesemann <grzm@myrealbox.com> writes:

Just a quick heads-up: I'm not sure of the cause, but it looks like
something recent change to HEAD and REL8_0_STABLE is causing check
failures on the buildfarm machines. A brief (and thoroughly naive)
glance at the details shows a horology test failure.

http://developer.postgresql.org/docs/postgres/regress-evaluation.html#AEN22575

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

------- End of Original Message -------

"Jim Buttafuoco" <jim@contactbda.com> writes:

Why doesn't the regression test set the timezone to GMT instead of PST. I believe the horology test would just work then.

... and lose any semblance of testing DST-aware behavior. Lobotomizing
the regression test isn't the answer.

(What is the answer, IMHO, is to make the interval datatype able to
distinguish "1 day" from "24 hours".)

regards, tom lane