Re: broken windows build
Hey, On Mon, Feb 16, 2015 at 2:38 PM, Eike Rathke er...@redhat.com wrote: Hi Markus, On Saturday, 2015-02-14 20:30:57 +0100, Markus Mohrhard wrote: I just disabled the test for now but please move it to subsequent_filters-test. Yeah, who would had thought of it.. ;-) Thanks for the interim fix, Jan is working on a solution. So I looked at the patch and decided it is best that I'll fix the part with the blank document. I already had a working solution but finally decided that it causes more trouble than benefit and went with a blank.ods file. The advantage of that approach is that without introducing any UNO stuff here (causing quite some pain with how to release the doc again) we get an empty document that has been initialized properly. I have pushed the patch now. Thanks a lot Jan for your work. I'm looking forward to your next patch. Regards, Markus ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: broken windows build
Hi Markus, On Saturday, 2015-02-14 20:30:57 +0100, Markus Mohrhard wrote: I just disabled the test for now but please move it to subsequent_filters-test. Yeah, who would had thought of it.. ;-) Thanks for the interim fix, Jan is working on a solution. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/ Care about Free Software, support the FSFE https://fsfe.org/support/?erack pgpFOGcyrrb07.pgp Description: PGP signature ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: broken windows build
On 02/10/2015 08:50 AM, Norbert Thiebaud wrote: since most likely http://ci.libreoffice.org/job/lo_tb_master_win/506/ one of the four patches involved there seems to cause the windows build to break and enter a cpu-loop in make, which cause a timeout... which does not apparently properly kill make, and therefore the tcp-server is hung too and can't serve other build. isn't Windaube wonderful ? That was 6 days ago.. that broke the window tb and every gerrit build attempt since then I regularly try to restart the windows slave.. which is not that easy to do remote, when one can only use lowercase without modifier (not Ctrl-C not | for instance) did I mentionned Windaube is wonderful ? But if no one care about build breakage... whats the point ? Maybe the tooling's output can be improved so that it becomes more apparent in http://ci.libreoffice.org/job/lo_tb_master_win/506/console that what actually happened was that make was killed upon a timeout. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
Re: broken windows build
On Tue, Feb 10, 2015 at 11:32 AM, Stephan Bergmann sberg...@redhat.com wrote: Maybe the tooling's output can be improved so that it becomes more apparent in http://ci.libreoffice.org/job/lo_tb_master_win/506/console that what actually happened was that make was killed upon a timeout. timing out from the client side (i.e jenkins here) is unreliable, so we try to time out from the server side... unfortunately the underlying make was not actually killed (which is the root cause of the subsequent woes) iow it did not work as intended.. so surely the output is not as hoped either... but one sure sign is the time the build took. if you look in 'Status' tab you'll see a running time of 3h00 which is the timeout value... while we are at it.. a running time 1min with a message about 'connection refused' is indication that there is a make that is stuck and prevent other build from starting... (not really a 'feature'.. but hey.. this is Windows... ) ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
