MachineSuite.TestMachinePrincipalUnits transient failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Per the duplicate bug and comment 2 of this bug:
The first fail is
Revision build: 2328 gitbranch:
The last pass for master is
Revision build: 2327 gitbranch:
The only suspect commit is
Commit 8020d93 Merge pull request #1586 from anastasiamac/
...
In a merge request of an unrelated change, I had a failure in: MachineSuite.
http://
-------
FAIL: machine_
SetUpTest
[LOG] 0:00.002 INFO juju.state opening state, mongo addresses: ["localhost:
[LOG] 0:00.002 DEBUG juju.state dialing mongo
[LOG] 0:00.003 INFO juju.mongo dialled mongo successfully on address "127.0.0.1:59080"
[LOG] 0:00.004 DEBUG juju.state connection established
[LOG] 0:00.026 INFO juju.mongo dialled mongo successfully on address "127.0.0.1:59080"
[LOG] 0:00.026 INFO juju.state initializing environment, owner: "test-admin@local"
[LOG] 0:00.026 INFO juju.state info: &mongo.
[LOG] 0:00.026 INFO juju.state starting presence watcher
[LOG] 0:00.028 INFO juju.mongo dialled mongo successfully on address "127.0.0.1:59080"
SetUpTest done
[LOG] 0:00.398 INFO juju.mongo dialled mongo successfully on address "127.0.0.1:59080"
test 0
test 1
test 2
machine_
c.Assert(
... obtained []string = []string{"s2/2", "s3/2"}
... expected []string = []string{"s2/2", "s3/1"}
[LOG] 0:00.513 INFO juju.testing reset successfully reset admin password
2015-02-12 09:49:35 INFO juju.testing mgo.go:514 reset successfully reset admin password
2015-02-12 09:50:08 INFO juju.testing mgo.go:514 reset successfully reset admin password
2015-02-12 09:50:22 INFO juju.testing mgo.go:514 reset successfully reset admin password
OOPS: 786 passed, 1 FAILED
--- FAIL: TestPackage (182.11 seconds)
FAIL
FAIL github.
I was not able to reproduce this locally, though, so I'm resubmitting the PR and submitting this bug so someone else has context in case it appears again.
Changed in juju-core: | |
milestone: | 1.21.3 → 1.23 |
description: | updated |
Changed in juju-core: | |
importance: | Critical → Medium |
milestone: | 1.23 → none |
tags: | added: unit-tests |
Changed in juju-core: | |
status: | Triaged → Fix Released |
I haven't been able to reproduce this, but as I also noticed a failure like this I asked frankban to add an explicit assert just before trying to use the units slice in that test (see http:// reviews. vapour. ws/r/919/). This is already in, so in case it happens again we might get closer to the cause (it looks like a flaky synchronization issue).