Fix for test-bus unit test on Windows while running the check_segfault_no_auto_start test

Yiyang Fei yiyangfei36 at yahoo.com
Tue Apr 26 16:05:40 UTC 2016


I opened a bug at https://bugs.freedesktop.org/show_bug.cgi?id=95155.
README.win indicates that some of the unit tests are known to fail, but did not include details on which test and why.  I am running the unit tests to ensure my build is production quality.  Test-bus is failing for the reason already indicated.  Test-dbus, test-spawn, and test-shutdown are also failing for other reasons I have yet to investigate.  Can you tell me if these tests are expected to pass?
Also, can a x86 application connect to a x64 dbus-daemon and communicate with a x64 application?  Our Windows install base are mostly x64 OS, so we will install x64 build of our app, including dbus, but there are customers who only builds x86 applications to run in Windows compatibility mode and still integrate with our applications.  If they compiled their x86 application with an x86 library we provide that communicates over dbus to the rest of our x64 applications, is this setup expected to work?
Thanks,Yiyang Fei  

    On Tuesday, April 26, 2016 6:58 AM, Simon McVittie <simon.mcvittie at collabora.co.uk> wrote:
 

 On 26/04/16 01:16, Yiyang Fei wrote:
> The test-bus unit test on Windows systems fails during the
> check_segfault_no_auto_start test.  The output of the error is as follows:
...
> check_segfault_service_no_auto_start:3043 received message interface
> "(unset)" member "(unset)" error name
> "org.freedesktop.DBus.Error.TimedOut" on 000001E176DAE0E0, expecting not
> this error
...
> Since test-segfault.exe application never claims the requested service,
> it makes sense that DBUS_ERROR_TIMED_OUT is returned.

No, this is not what is expected. We should be able to detect that the
activated subprocess has failed (exited abnormally or with exit status
not 0), and report that, immediately; we should not have to wait for an
arbitrary timeout.

I assume you also see a noticeable (multiple seconds) delay before the
message "Failed to activate service
'org.freedesktop.DBus.TestSuiteSegfaultService': timed out"?

This works on Unix, and this is the first I've heard about it failing on
Windows. (Ralf, presumably this test works OK for you?)

Please open a bug in
<https://bugs.freedesktop.org/enter_bug.cgi?product=dbus&component=core>. That's
also the way to ask for a patch to be applied, but in this case I don't
think your proposed patch is the correct change.

Thanks,
    S
-- 
Simon McVittie
Collabora Ltd. <http://www.collabora.com/>

_______________________________________________
dbus mailing list
dbus at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dbus


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dbus/attachments/20160426/3f2bb15e/attachment.html>


More information about the dbus mailing list