CppunitTest_sw_layoutwriter failing on Windows with HiDPI

Patrick Jaap patrick.jaap at tu-dresden.de
Tue Sep 17 10:01:50 UTC 2019


Hi! 

In my commit I tested for fly portions. Is this really the right commit?

And I don't know in what specific environment the unit tests should be 
executed. Do we take display scaling into account?

Best,
Patrick



Am Sonntag, 15. September 2019, 03:52:01 CEST schrieb Luke Benes:
> The Unit Test added in
> https://cgit.freedesktop.org/libreoffice/core/commit/?id=4ac31078b9c46231f8e
> cf0409a1724749ac8c5a4
> 
> Is causing the core Unit Test CppunitTest_sw_layoutwriter to fail when you
> set,  Settings->Display->Scale=125% in Windows 10.
> 
> 
> 
> horizontal_multilevel.odt:
> C:/lode/dev/core/test/source/xmltesttools.cxx(168) : error : Assertion
> Test name: testHorizontal_multilevel::TestBody
> equality assertion failed
> - Expected: 7945
> - Actual  : 7946
> - In <>, attribute 'y' of
> '/metafile/push[1]/push[1]/push[1]/push[3]/push[1]/textarray[7]' incorrect
> value.
> 
> Failures !!!
> Run: 56   Failure total: 1   Failures: 1   Errors: 0
> 
> Error: a unit test failed, please do one of:
> make CppunitTest_sw_layoutwriter CPPUNITTRACE=TRUE # which is a shortcut for
> the following line make CppunitTest_sw_layoutwriter
> CPPUNITTRACE="'C:/Program Files (x86)/Microsoft Visual
> Studio/2017/Community/Common7/IDE/devenv.exe' /debugexe" # for interactive
> debugging in Visual Studio make CppunitTest_sw_layoutwriter
> CPPUNITTRACE="drmemory -free_max_frames 20" # for memory checking (install
> Dr.Memory first, and put it to your PATH)
> 
> You can limit the execution to just one particular test by:
> 
> make CppunitTest_sw_layoutwriter CPPUNIT_TEST_NAME="testXYZ" ...above
> mentioned params...
> 
> make[1]: *** [C:/lode/dev/core/solenv/gbuild/CppunitTest.mk:114:
> C:/lode/dev/core/workdir/CppunitTest/sw_layoutwriter.test] Error 1 make:
> *** [Makefile:167: CppunitTest_sw_layoutwriter] Error 2




More information about the LibreOffice mailing list