Re: Buildfarm issues on specific machines

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: darcy(at)dbitech(dot)ca, remi_zara(at)mac(dot)com, books(at)ejurka(dot)com, markw(at)osdl(dot)org, decibel(at)decibel(dot)org, pete(at)economics(dot)utoronto(dot)ca, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Buildfarm issues on specific machines
Date: 2005-07-17 18:31:56
Message-ID: 21750.1121625116@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> I believe that if we do something like
>>
>> TEMP_PORT = 5$(default_port)
>>
>> check:
>> pg_regress ... --temp_port=$(TEMP_PORT)
>>
>> then the port could be overridden without any source code hacks by
>> "gmake TEMP_PORT=nnn check".

> Works for me. Let's do it. If I understand this right it would not need
> any changes on the buildfarm side.

Done as far back as 7.4, so that this should actually work as long as
you don't try to parallel-test 7.3 and 7.2.

The buildfarm config stuff should recommend choosing 4-digit port
numbers, because the patch I put in will fall back to 65432 if the
configuration port is 5 digits.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-07-17 18:56:12 Minor buildfarm HOWTO comment
Previous Message Andrew Dunstan 2005-07-17 16:26:12 Re: Buildfarm issues on specific machines