Hi Aaron,

On  Fr 27 Okt 2017 15:14:15 CEST, Aaron M. Ucko wrote:

> Source: libqtdbustest
> Version: 0.2+bzr42+repack1-1
> Severity: important
> Tags: upstream
> Justification: fails to build from source
>
> Builds of libqtdbustest for most architectures failed:
>
>   [  PASSED  ] 4 tests.
>   [  FAILED  ] 2 tests, listed below:
>   [  FAILED  ] TestDBusTestRunner.StartsSessionService
>   [  FAILED  ] TestQProcessDBusService.WaitsForServiceAppeared
>
>    2 FAILED TESTS
>
> These tests all encountered stack traces along the lines of
>
>   Traceback (most recent call last):
>     File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
>       "__main__", mod_spec)
>     File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
>       exec(code, run_globals)
>     File "/usr/lib/python3/dist-packages/dbusmock/__main__.py", line  
> 81, in <module>
>       bus = dbusmock.testcase.DBusTestCase.get_dbus(args.system)
>     File "/usr/lib/python3/dist-packages/dbusmock/testcase.py", line  
> 150, in get_dbus
>       return dbus.bus.BusConnection(os.environ['DBUS_SESSION_BUS_ADDRESS'])
>     File "/usr/lib/python3/dist-packages/dbus/bus.py", line 122, in __new__
>       bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
>   dbus.exceptions.DBusException:  
> org.freedesktop.DBus.Error.BadAddress: '=' character not found or  
> has no value following it
>   unknown file: Failure
>   C++ exception with description "Process [/usr/bin/python3] for  
> service [test.session.name] failed to appear on bus" thrown in the  
> test body.
>
> though in some cases the error was instead
>
>   dbus.exceptions.DBusException:  
> org.freedesktop.DBus.Error.BadAddress: Could not parse server  
> address: Unknown address type (examples of valid types are "tcp" and  
> on UNIX "unix")
>
> This latter variant occurred for StartsSessionService on armel and for
> WaitsForServiceAppeared on s390x, as respectively detailed at
>
> https://buildd.debian.org/status/fetch.php?pkg=libqtdbustest&arch=armel&ver=0.2%2Bbzr42%2Brepack1-1&stamp=1509080424&raw=0
> https://buildd.debian.org/status/fetch.php?pkg=libqtdbustest&arch=s390x&ver=0.2%2Bbzr42%2Brepack1-1&stamp=1509012596&raw=0
>
> I also see errors along these lines in ThrowsErrorForFailToStart,
> which I suspect is succeeding for the wrong reason.
>
> Could you please take a look?
>
> Thanks!

Funny enough, I saw the same error on amd64 1.5 weeks ago. Without  
knowing where they came from. I put aside the package for 3-4 days and  
set back on it again. Did a test build and... things worked.  
Reproducibly.

Sooo... My assumption was, that this was related to some package  
upgrades in the archive. Maybe packages that have not reached the  
archtitectures, that showed the test failures on buildd.

My strategy for now would be to ask for a give back in two weeks of  
time and then see...

Mike
-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

