Am 21. Mai 2019 00:48:40 MESZ schrieb Regina Henschel <rb.henschel@t-online.de>:
I get curious results.
If I run the single test using
/opt/lo/bin/make CppunitTest_sd_misc_tests
CPPUNIT_TEST_NAME="testTdf119956" CPPUNITTRACE=TRUE
or
/opt/lo/bin/make CppunitTest_sd_misc_tests
CPPUNIT_TEST_NAME="testTdf119956"
it does _not_ fail.
If I run the test among other tests using
$ /opt/lo/bin/make sd.check
it fails.
...
But that does not explain, why the test works here as single test and
not in the series of tests.
There is a general problem with LO unit tests: a test may change the state of the application,
which eventually influences the next test. Some stuff is cached.
In theory you would have to restart LO for each test to reset any internal state, but that would be
very slow.
The other, more probable possibility, I have also faced a few times, is memory corruption. This
means your failing test is actually valid, but a previous test has passed but corrupted some
memory. You should run the whole test in some memory checker.
Jan-Marek
Context
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.