Date: prev next · Thread: first prev next last
2019 Archives by date, by thread · List index


Am 14.07.19 um 13:28 schrieb Kaganski Mike:
I see sw_uiwriter hanging locally in 
testDateFormFieldCurrentDateInvalidation (added in commit 
d0ff1090762ac61ce08f54bc76685232699d98a0), never returning from 
Scheduler::ProcessEventsToIdle. Killing the test after some time 
produces multiple lines in console:

warn:vcl.schedule:5488:13820:vcl/source/app/svapp.cxx:470: ProcessEventsToIdle: 1000
warn:vcl.schedule:5488:13820:vcl/source/app/svapp.cxx:470: ProcessEventsToIdle: 2000
...
warn:vcl.schedule:5488:13820:vcl/source/app/svapp.cxx:470: ProcessEventsToIdle: 845000

I believe that's the reason for massive number of aborted Windows 
jenkins builds that lately affect our CI (just the last few are builds 
#34586, #34587, #34588, #34589, #34590, #34591).

Just see the list in https://ci.libreoffice.org/job/gerrit_windows/

And https://gerrit.libreoffice.org/75463 was force-pushed after an Abort.

I know there are still problems with the Scheduler code on Windows, eventually
the AnyInput handling. Probably it's the same then
https://bugs.documentfoundation.org/show_bug.cgi?id=123583
My guess is LO is generating system events, so processing is always interrupted.

Also see https://gerrit.libreoffice.org/#/c/75568/

I can help debugging the general problem, but since I don't have Windows or a
Windows build, I can't do it myself.

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.