From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
---|---|
To: | Mikael Kjellström <mikael(dot)kjellstrom(at)mksoft(dot)nu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, buildfarm-members(at)postgresql(dot)org |
Subject: | Re: Reminder: spin up REL_11_STABLE on your buildfarm animals |
Date: | 2018-07-09 13:11:52 |
Message-ID: | 3866aa74-5b40-83b2-0c6a-6579da2e501f@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | buildfarm-members |
On 07/09/2018 08:09 AM, Mikael Kjellström wrote:
> On 2018-07-09 13:31, Andrew Dunstan wrote:
>
>> run_branches has a global lock that protects against concurrent runs
>> of different animals. You just point all the animals on the machine
>> at the same lock directory. I have several machines with this setup.
>> See global_lock_dir in the sample config file.
>
> Yes, that would work if the animals run in the same
> OS-instance/virtual machine.
>
> All my animals is running different OS (OpenBSD, FreeBSD, NetBSD,
> DragonFlyBSD etc.) and in different virtual machines.
>
>
Fair enough. I'll make a note that we need to notify buildfarm owners
explicitly.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2018-08-17 21:27:42 | many animals are running old clients |
Previous Message | Mikael Kjellström | 2018-07-09 12:09:51 | Re: Reminder: spin up REL_11_STABLE on your buildfarm animals |