Re: minor windows & cygwin regression failures on stable

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: jim(at)contactbda(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: minor windows & cygwin regression failures on stable
Date: 2005-03-26 16:22:02
Message-ID: 42458C2A.2090703@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Jim,

that is just execllent! Thank you so much! I assume you mean XP-Pro - I
gather that user permissions get in the way on XP-HE.

We can make the one machine do double duty for Windows and Cygwin.

You will need installed:
. cygwin, including whatever it takes to build cygwin postgres
. native perl (ActiveState perl works just fine)
. normal native windows postgres build environment (MSys, Mingw,
MSysDTK etc).

After that we'll explore a bit what it takes to automate the buildfarm
processes on Windows. You and I can do that offline.

Let's get this going first and then look at W2K.

cheers

andrew

Jim Buttafuoco wrote:

>Andrew,
>
>I can set one up a dedicated windows XP system on monday. I also have some w2k systems that can be used.Are there
>directions anywhere?
>
>Jim
>
>
>---------- Original Message -----------
>From: Andrew Dunstan <andrew(at)dunslane(dot)net>
>To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
>Sent: Fri, 25 Mar 2005 22:19:25 -0500
>Subject: Re: [HACKERS] minor windows & cygwin regression failures on stable
>
>
>
>>Tom Lane wrote:
>>
>>
>>
>>>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>>
>>>
>>>
>>>
>>>>Windows has ordering failures on the join and rules tests - Cygwin has a
>>>>failures on the stats test. See buildfarm for details.
>>>>
>>>>
>>>>
>>>>
>>>The ordering failures seem to be because the recent planner hacking has
>>>taken us back to preferring merge joins for these tests, and Windows'
>>>version of qsort has bizarre behavior for equal keys.
>>>
>>>I put an ORDER BY in the rules test. For join, I'm inclined to think
>>>that the best bet is to resurrect the join_1.out variant comparison
>>>file that we had awhile ago. Unfortunately, what's in the CVS archives
>>>is out of date and can't be used directly. Could you send me the actual
>>>rules.out you get on Windows to use for a comparison file?
>>>
>>>
>>>
>>>
>>join.out sent off list
>>
>>
>>
>>>Dunno about the stats failure. It looks like the stats collector just
>>>isn't working on Cygwin, but AFAIR no one has touched that code lately.
>>>
>>>
>>>
>>>
>>It's worked before, that's the strange thing. I'll check some more.
>>
>>
>>
>>>Do these machines fail on HEAD too? (There don't seem to be any active
>>>Windows buildfarm machines for HEAD, which is surely ungood. Won't
>>>someone step up and put one into the regular rotation?)
>>>
>>>
>>>
>>>
>>>
>>>
>>Sufficient unto the day is the evil thereof (appropriate quotation for
>>Good friday). I will address HEAD in due course.
>>
>>The buildfarm members for both of these are in reality my laptop, which
>>doesn't even run Windows all the time, and has lots of other duties
>>anyway. We (or rather Josh Berkus and Bruce, at my request) are looking
>>for a replacement.
>>
>>cheers
>>
>>andrew
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 5: Have you checked our extensive FAQ?
>>
>> http://www.postgresql.org/docs/faq
>>
>>
>------- End of Original Message -------
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-03-26 17:59:48 Re: [PATCHES] problem with CR+LF in files in psql \i command
Previous Message Stephan Szabo 2005-03-26 16:16:01 Re: Patch for collation using ICU