Intermittent TestUniterRelations failure
Bug #1265875 reported by
Casey Marshall
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
William Reade |
Bug Description
Encountered a uniter test failure during a merge proposal build, which seems to be an intermittent issue unrelated to the merge. I am not able to reproduce in my development environment, nor did it recur when manually run on the build server.
See the log at: https:/
tags: | added: intermittent-failure test-failure |
summary: |
- Intermittent uniter test failure + Intermittent TestUniterRelations failure |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
I've seen another intermittent TestUniterRelations failure, which I'm adding under this bug because they might both be related:
test 5: unit becomes dead while in a relation
step 0:
uniter_ test.quickStart Relation{ } test.quickStart {} test.createChar m{revision: 0, badHooks: []string( nil), customize: (func(* gocheck. C, *uniter_ test.context, string))(nil)} test.addCharm{ dir:(*charm. Dir)(0xc21026ae a0), curl:(* charm.URL) (0xc210732a00) } test.serveCharm {} test.createUnit er{} test.ensureStat eWorker{ } test.createServ iceAndUnit{ serviceName: ""} test.startUnite r{unitTag: ""} test.waitAddres ses{} test.waitUnit{ status: "started" , info:"", data:params. StatusData( nil), charm:0, resolved:""} test.waitHooks{ "install" , "config-changed", "start"} test.verifyChar m{revision: 0, dirty:false} test.waitHooks{ } test.addRelatio n{waitJoin: false} test.addRelatio nUnit{} test.waitHooks{ "db-relation- joined mysql/0 db:0", "db-relation- changed mysql/0 db:0"} changed mysql/0 db:0"} changed mysql/0 db:0"} test.verifyRunn ing{noHooks: false} test.stopUniter {err:"" } test.startUnite r{unitTag: ""} test.waitHooks{ "config- changed" } changed mysql/0 db:0", "config-changed"} changed mysql/0 db:0"} changed mysql/0 db:0"} changed mysql/0 db:0", "config-changed"}
uniter_
uniter_
uniter_
uniter_
uniter_
uniter_
uniter_
API: login as "unit-u-0" successful
uniter_
uniter_
uniter_
want unit status "started", got "pending"; still waiting
want unit status "started", got "pending"; still waiting
want unit status "started", got "pending"; still waiting
want unit status "started", got "installed"; still waiting
want unit status "started", got "installed"; still waiting
uniter_
waiting for hooks: []string{"install", "config-changed", "start"}
ctx.hooksCompleted: []string{"install", "config-changed", "start"}
uniter_
uniter_
waiting for hooks: []string{"install", "config-changed", "start"}
ctx.hooksCompleted: []string{"install", "config-changed", "start"}
uniter_
uniter_
uniter_
waiting for hooks: []string{"install", "config-changed", "start", "db-relation-joined mysql/0 db:0", "db-relation-
ctx.hooksCompleted: []string{"install", "config-changed", "start"}
ctx.hooksCompleted: []string{"install", "config-changed", "start"}
ctx.hooksCompleted: []string{"install", "config-changed", "start", "db-relation-joined mysql/0 db:0"}
ctx.hooksCompleted: []string{"install", "config-changed", "start", "db-relation-joined mysql/0 db:0", "db-relation-
uniter_
uniter_
uniter_
uniter_
waiting for hooks: []string{"install", "config-changed", "start", "db-relation-joined mysql/0 db:0", "db-relation-
ctx.hooksCompleted: []string{"install", "config-changed", "start", "db-relation-joined mysql/0 db:0", "db-relation-
ctx.hooksCompleted: []string{"install", "config-changed", "start", "db-relation-joined mysql/0 db:0", "db-relation-
ctx.hooksCompleted: []string{"install", "config-changed", "start", "db-relation-joined mysql/0 db:0", "db-relation-
step 1:
uniter_ test.custom{ f:(func( *gocheck. C, *uniter_ test.context) )(0x45d290) }
step 2:
uniter_ test.waitUniter Dead{err: ""} test.startUnite r{unitTag: ""} test.go: 1026: Tests(c, relationsTests) test.go: 1392: ErrTerminateAge nt)
uniter_
uniter_
s.runUniter
uniter_
c.Assert(err, gc.Equals, worker.
... obtained *erro...