Strange Rabbit exception output in test suite
Bug #1225981 reported by
Jeroen T. Vermeulen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Low
|
Gavin Panella | ||
Bug Description
When running the test suite on Saucy, we see output like:
Exception socket.error: (107, 'Transport endpoint is not connected') in <bound method TCPTransport.
It's been spotted even on successful test runs, so we believe it may be harmless apart from the distraction.
The output may or may not be related to bug 1225980. The provisional workaround for that bug did not hide this output.
Related branches
lp://qastaging/~allenap/maas/silence-amqplib-warnings
- Julian Edwards (community): Approve
-
Diff: 68 lines (+11/-1)1 file modifiedsrc/maasserver/tests/test_rabbit.py (+11/-1)
Revision history for this message
| Gavin Panella (allenap) wrote | #1 |
| Changed in maas: | |
| importance: | Critical → Low |
Revision history for this message
| Jeroen T. Vermeulen (jtv) wrote | #2 |
| Changed in maas: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Gavin Panella (allenap) |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| milestone: | none → 14.04 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Indeed, this is harmless. It's insufficiently robust code in amqplib. It's in a __del__() method so the error gets printed, but it has no repercussions.