On 08/07/2012 07:31 AM, Tor Lillqvist wrote:
Michael Stahl has discovered that a unit test deadlocks on Windows -- I'm
currently looking into why that occurs.
Dunno about deadlocks, but in my Windows build during the night the
sd_filters_test apparently got stuck in a loop, filling my disk by
writing an endless stream of
DiscoveryService received a packet.
DiscoveryService waiting for packet
to the sd_filters_test.test.log file...
--tml
The networking is started as soon as sddll is loaded -- and at the
moment doesn't ever stop -- i.e the server component will just keep
listening for clients permanently -- I assume that's what's causing the
problems with unit tests on windows (they appear to run fine on my linux
machine), I'm not entirely sure how to fix that though.
(It looks like you might have something sending multicast packets on
port 1598, which is probably why you keep seeing the packets being
received. Alternatively there is an error every time I call receive,
which I don't handle yet, which would result in such looping too. The
port number was arbitrary and just for testing.)
Cheers,
Andrzej
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.