(In reply to Björn Michaelsen from comment #13)
> workdir/JunitTest/sw_complex/done.log
> workdir/JunitTest/sfx2_complex/done.log
> workdir/JunitTest/framework_complex/done.log
Rerunning these standalone show the 1 OutputDevice, 1 VirtualDevice from other tests. Curious.
(In reply to Björn Michaelsen from comment #12)
> - This run also excludes CppunitTest_sw_mailmerge which might be looping (or
> excessively slow). I killed it after some 10 CPU minutes.
Rerunning standalone showed no issues. Thus:
> - This run also excludes CppunitTest_vcl_wmf_test which crashes on a our_vAllVclPtrs.remove(this) on exit, which shouldnt happen.
and chart2_unoapi leaking OpenGL and a window. are the only remaining issue. Once that is fixed, we _could_ think about adding the attached patch to debug builds and make those barf up if more than the expected 1 OutputDevice, 1 VirtualDevice are left over. This should help detect regressions early.
(In reply to Björn Michaelsen from comment #13) JunitTest/ sw_complex/ done.log JunitTest/ sfx2_complex/ done.log JunitTest/ framework_ complex/ done.log
> workdir/
> workdir/
> workdir/
Rerunning these standalone show the 1 OutputDevice, 1 VirtualDevice from other tests. Curious.
(In reply to Björn Michaelsen from comment #12) sw_mailmerge which might be looping (or
> - This run also excludes CppunitTest_
> excessively slow). I killed it after some 10 CPU minutes.
Rerunning standalone showed no issues. Thus:
> - This run also excludes CppunitTest_ vcl_wmf_ test which crashes on a our_vAllVclPtrs .remove( this) on exit, which shouldnt happen.
and chart2_unoapi leaking OpenGL and a window. are the only remaining issue. Once that is fixed, we _could_ think about adding the attached patch to debug builds and make those barf up if more than the expected 1 OutputDevice, 1 VirtualDevice are left over. This should help detect regressions early.