Bug 44020

Summary: FAIL: avahi/tubes/two-muc-stream-tubes.py - test failing in buildbot
Product: Telepathy Reporter: Alvaro Soliverez <alvaro.soliverez>
Component: salutAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED FIXED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium Keywords: patch
Version: git master   
Hardware: Other   
OS: All   
URL: http://cgit.freedesktop.org/~jonny/telepathy-salut/commit/?h=44020-unix-path
Whiteboard: review+
i915 platform: i915 features:

Description Alvaro Soliverez 2011-12-21 07:29:10 UTC
Traceback (most recent call last):
  File "/var/lib/buildbot/telepathy/salut-default-amd64/build/build/telepathy-salut-0.7.0.1/tests/twisted/saluttest.py", line 135, in exec_test_deferred
    fun(queue, bus, conn)
  File "../../../tests/twisted/avahi/tubes/two-muc-stream-tubes.py", line 64, in test
    l = reactor.listenUNIX(server_socket_address, factory)
  File "/usr/lib/python2.6/dist-packages/twisted/internet/posixbase.py", line 380, in listenUNIX
    p.startListening()
  File "/usr/lib/python2.6/dist-packages/twisted/internet/unix.py", line 120, in startListening
    raise CannotListenError, (None, self.port, le)
CannotListenError: Couldn't listen on any:/var/lib/buildbot/telepathy/salut-default-amd64/build/build/telepathy-salut-0.7.0.1/_build/tests/twisted/stream: AF_UNIX path too long.
FAIL: avahi/tubes/two-muc-stream-tubes.py


See here for more details: http://buildbot.telepathy.im/builders/telepathy-salut%20-%20amd64/builds/67
Comment 1 Jonny Lamb 2012-01-05 05:49:37 UTC
Gabble has exactly the same problem at bug #43981.

Here's a similar fix to the one I proposed to gabble.
Comment 2 Alvaro Soliverez 2012-01-30 04:57:36 UTC
Can someone review and push if approved?
I don't have push access to this repo.

Thanks!
Comment 3 Simon McVittie 2012-01-30 10:35:40 UTC
r+
Comment 4 Jonny Lamb 2012-01-30 11:43:25 UTC
Many thanks, merged.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.