Re: Bison 3.0 updates

From: Marti Raudsepp <marti(at)juffo(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PGBuildFarm <pgbuildfarm-members(at)pgfoundry(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bison 3.0 updates
Date: 2013-07-29 18:26:11
Message-ID: CABRT9RCW9M4ZUHVXKkrYhF8uYs9bYc0-K_d1v-71gbo_NTHfJA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: buildfarm-members pgsql-hackers

On Mon, Jul 29, 2013 at 9:15 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> There has to be something between "set in stone and never changes" and
> "auto-updates everything every 24 hours" that would suit us.

Well sure I could change the update frequency. But again, it seems
like delaying the inevitable.

> I'm toying with the idea of a check_upgrade mode for the buildfarm client
> where it wouldn't do a git pull, but would report changes if the build
> result was different from the previous result. You'd run this immediately
> after pulling new changes into your OS. Other, brighter ideas welcome.

What would be the right course of action if check_upgrade fails? Is it
reasonable to expect buildfarm volunteers to downgrade the system and
postpone until the problem is resolved?

Or do you think the member should be removed from the farm until the
build succeeds again? Sounds like worst of both worlds.

Regards,
Marti

In response to

Responses

Browse buildfarm-members by date

  From Date Subject
Next Message Andrew Dunstan 2013-07-29 18:45:22 Re: Bison 3.0 updates
Previous Message Andrew Dunstan 2013-07-29 18:15:31 Re: Bison 3.0 updates

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2013-07-29 18:45:22 Re: Bison 3.0 updates
Previous Message Jeff Janes 2013-07-29 18:25:15 Re: maintenance_work_mem and CREATE INDEX time