Hello,
On 25/6/21 10:10, Thorsten Behrens
wrote:
it turned out it was introduced by b9ea3467383ccdfe4be842e61267256f281487ee <+ tests that failed more than twice in last seven days: 3 CppunitTest_sw_ww8export gerrit_windows 3 UITest_calc_tests3 gerrit_linux_clang_dbgutil 3 UITest_sw_sidebar gerrit_linux_clang_dbgutil 4 UITest_calc_tests gerrit_linux_clang_dbgutil 4 UITest_impress_demo gerrit_linux_clang_dbgutil 4 UITest_signatureLine gerrit_linux_clang_dbgutil 5 CppunitTest_chart2_import gerrit_windows 6 CppunitTest_writerperfect_writer gerrit_windows 7 CppunitTest_sw_core_undo gerrit_windows 8 CppunitTest_sc_uicalc gerrit_windows 9 UITest_writer_tests7 gerrit_linux_clang_dbgutil 54 Killed by the kill-wrapper gerrit_linux_clang_dbgutil - is that all uitest-induced? Yes - perhaps add the log file too, on the killwrapper output? - additional hints on zeroing on on the actual test might be from the mass-rework, i.e. smaller test scopes - https://gerrit.libreoffice.org/c/core/+/117752 revert hopefully will fix the problem - https://gerrit.libreoffice.org/c/core/+/117392 might also be problematic (along with other uitest guard ones?)
svp: always release SolarMutex on yield
> and it got fixed by 4abd2598f7816891af3bd462ffaee57f3423b9f9
<
Revert: svp: always release SolarMutex
on yield >
Regards
-- Xisco Faulí LibreOffice QA Team IRC: x1sc0
_______________________________________________ LibreOffice mailing list LibreOffice@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/libreoffice