Subsequent Test PythonTest_dbaccess_python stuck in Infinite Loop

Luke Benes <lukebenes -AT- hotmail.com>
Thu, 10 May 2018 13:33:16 +0000


When you do a 'make check' under Windows, recent builds never finish. I have narrowed this 
regression to 

https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=88748175..de3d0569

pointing to

https://cgit.freedesktop.org/libreoffice/core/commit/?id=1c5c9b84df270e41c68e68bb69fbf183fc20eed2

Here is the error when you kill python.exe

[build SCK] xmloff

Error: a unit test failed, please do one of:

make PythonTest_dbaccess_python CPPUNITTRACE="gdb --args"
    # for interactive debugging on Linux
make PythonTest_dbaccess_python VALGRIND=memcheck
    # for memory checking
make PythonTest_dbaccess_python DEBUGCPPUNIT=TRUE
    # for exception catching

You can limit the execution to just one particular test by:

make PYTHON_TEST_NAME="testXYZ" ...above mentioned params...

make[1]:
Makefile:286: recipe for target 'build' failed
make: *** [build] Error 2

Context

Subsequent Test PythonTest_dbaccess_python stuck in Infinite Loop · Luke Benes
- Re: Subsequent Test PythonTest_dbaccess_python stuck in Infinite Loop · Kaganski Mike
  - Re: Subsequent Test PythonTest_dbaccess_python stuck in Infinite Loop · slacka
- (message not available)
  - Re: Subsequent Test PythonTest_dbaccess_python stuck in Infinite Loop · Tamas Bunth

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.