This will also be why the wily CI tests don't pass as wily has Go 1.5
Tim
On 16/09/15 16:53, Tim Penhey wrote:
> Hi all,
>
> Using Go 1.5 on trusty has the peergrouper tests failing very often. 1
> or 2 almost every time.
>
> Dave suggested trying "GOMAXPROCS=1" which will make the scheduler
Here is an approach that will work for now:
http://reviews.vapour.ws/r/2672/diff/# - a 1.25 based branch
If we are happy with this, I can forward port to master and add the
other upgrade step.
Also, do we want to back port to 1.24?
When is the 1.24.6 release?
Tim
On 16/09/15 16:45, Ian Booth
On 16/09/15 12:06, Menno Smits wrote:
> On 16 September 2015 at 08:41, Tim Penhey wrote:
>
>> On 15/09/15 19:38, William Reade wrote:
>>> Having the machine agent run unit agent upgrade steps would be a Bad
>>> Thing -- the unit agents are still actively running the
On 16 September 2015 at 08:41, Tim Penhey wrote:
> On 15/09/15 19:38, William Reade wrote:
> > Having the machine agent run unit agent upgrade steps would be a Bad
> > Thing -- the unit agents are still actively running the old code at that
> > point. Stopping the unit
Having the machine agent run unit agent upgrade steps would be a Bad Thing
-- the unit agents are still actively running the old code at that point.
Stopping the unit agents and managing the upgrade purely from the machine
would be ok; but it feels like a lot of effort for very little payoff, so