intermittent unit failure: workerSuite.TestSetsAndUpdatesMembers

[Anastasia]

As per http://ci.jujucharms.com/blue/organizations/jenkins/github-merge-juju/detail/github-merge-juju/26/pipeline

[John A Meinel (jameinel)]

Also seen here:
 http://ci.jujucharms.com/job/github-merge-juju/76/console

On Fri, Feb 9, 2018 at 11:56 AM, Anastasia <email address hidden>
wrote:

> Public bug reported:
>
> As per http://ci.jujucharms.com/blue/organizations/jenkins/github-merge-
> juju/detail/github-merge-juju/26/pipeline
>
> ** Affects: juju
> Importance: Medium
> Status: Triaged
>
>
> ** Tags: intermittent-failure unit-tests
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1748385
>
> Title:
> intermittent unit failure: workerSuite.TestSetsAndUpdatesMembers
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1748385/+subscriptions
>

[John A Meinel (jameinel)]

http://ci.jujucharms.com/job/github-check-merge-juju/217/console

[John A Meinel (jameinel)]

I did a bunch of investigation, only to find out that it seems Tim had already done a patch on 2.3 (where I thought I was seeing this fail, but I was actually only seeing it fail when *merging* 2.3 into develop.)

It turns out that whatever patch Tim had done actually got reverted in merging into develop. Probably because Andrew had also been working in that area.

But I have a patch for 2.3 that at least makes all of the peergrouper logging *much* cleaner, and then we can make sure that we get 2.3 merged into develop and have the new infrastructure.

[John A Meinel (jameinel)]

Cleanup into 2.3 https://github.com/juju/juju/pull/8410
Cleanup and test fix into 2.4 https://github.com/juju/juju/pull/8411