rpc: intermittent test failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Expired
|
Low
|
Unassigned |
Bug Description
It seems it happens rarely (seen once so far - subsequent runs of the tests pass). Seen at r947, but probably was there before that.
FAIL: rpc_test.go:408: suite.TestBadCall
[LOG] 37.26191 JUJU rpc: discarding obtainer method reflect.
[LOG] 37.26196 JUJU rpc: discarding obtainer method reflect.
[LOG] 37.26200 JUJU rpc: discarding obtainer method reflect.
[LOG] 37.26253 JUJU send client request header: &rpc.Request{
[LOG] 37.26272 JUJU send client request body: struct {}{}
[LOG] 37.26278 JUJU got response header &rpc.Response{
rpc_test.go:417:
[LOG] 37.26292 JUJU rpc: client protocol error: read tcp [::1]:35405: connection reset by peer
c.Assert(err, ErrorMatches, `server error: unknown object type "BadSomething"`)
... error string = "write tcp [::1]:35405: broken pipe"
... regex string = "server error: unknown object type \"BadSomething\""
OOPS: 8 passed, 1 FAILED
--- FAIL: TestAll (0.06 seconds)
tags: | added: intermittent-failure |
tags: | added: needs-confirmation test-failure |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Low |
This is now really old and I can't recall seeing it reappear so marking as Incomplete. We can reopen if required.