TestSetsAndUpdatesMembers timed out

[Curtis Hovey]

As seen in
    http://reports.vapour.ws/releases/issue/5617dbc6749a562f5cdd8efc
TestSetsAndUpdatesMembers timed out

worker_test.go:515:
    c.Fatalf("timed out waiting for value to be set")
... Error: timed out waiting for value to be set

worker_test.go:123:
    c.Check(worker.Stop(w), gc.IsNil)
... value *errors.errorString = &errors.errorString{s:"cannot compute desired peer group: voting non-machine member replicaset.Member{Id:0, Address:\"[2001:DB8::10]:1234\", Arbiter:(*bool)(nil), BuildIndexes:(*bool)(nil), Hidden:(*bool)(nil), Priority:(*float64)(nil), Tags:map[string]string{\"juju-machine-id\":\"10\"}, SlaveDelay:(*time.Duration)(nil), Votes:(*int)(nil)} found in peer group"} ("cannot compute desired peer group: voting non-machine member replicaset.Member{Id:0, Address:\"[2001:DB8::10]:1234\", Arbiter:(*bool)(nil), BuildIndexes:(*bool)(nil), Hidden:(*bool)(nil), Priority:(*float64)(nil), Tags:map[string]string{\"juju-machine-id\":\"10\"}, SlaveDelay:(*time.Duration)(nil), Votes:(*int)(nil)} found in peer group")

This is seen in all series and archs that test go1.5

[Cheryl Jennings (cherylj)]

Seems to have been fixed on master as it hasn't been seen except in 1.25 since Nov 2015.

[Curtis Hovey (sinzui)]

As of December 9th 2016, this issue is seen several times a week in juju 2.x.