[Bug 30565] test failures: "error: getsockaddrarg: bad family"

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=30565

Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|telepathy-gabble-0.10.2:    |test failures: "error:
                   |make check fails due        |getsockaddrarg: bad family"
                   |twisted tests problem       |

--- Comment #10 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
Are the tests being run automatically, or because you have specifically asked
for them?

I do not recommend running the telepathy-gabble regression tests in an
automated build system like Debian buildds, even if there is a policy of
"usually" running regression tests: they're too prone to race conditions.

I particularly do not recommend running these regression tests in an end-user
build system like Gentoo portage or BSD ports. in their current state, they
should only be run by people who're willing and able to debug them.

>     assert len(debug.GetMessages()) > 0
> AssertionError
> FAIL: test-debug.py

Bug #45986. Workaround: don't configure telepathy-glib with
--disable-debug-cache.

> TimeoutError
> FAIL: jingle-share/test-send-file-send-before-accept.py

Bug #49595. I'm probably going to knock out that test until someone has time to
find and fix its race conditions.

>   File "/usr/lib64/python2.7/socket.py", line 224, in meth
>     return getattr(self._sock,name)(*args)
> error: getsockaddrarg: bad family

Er... wild guess: did you configure Python without IPv6 support? (If so, "don't
do that, then".)

Let's use this bug number to represent the "getsockaddrarg" stuff, since the
rest already has another bug.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.