Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Hi Erike

Every so often I compile and test LibreOffice to ensure that no regressions have occurred. I've encountered a few over the years that have even got into the Still version of LibreOffice.

As to whatever CHIINV and MINVERSE does doesn't bother me I don't use them at all. So, I just delete the offending test in the .fods file and move on. I never push anything back. That way if any other tests fail I'll know about them

On my day job I've got a deadline looming for this Friday, 16th August 2016. Once that's out of the way, I may have another look at CHIINV next week. I'm intrigued why the same binary of LO 5.1.4.2 works on some environments but not on others.

Alex

On 14/09/16 16:52, Eike Rathke wrote:
Hi Alex,

On Wednesday, 2016-09-14 08:56:21 +0200, Eike Rathke wrote:

1. either stepping through the code
Well, you can try, but it's a more general problem not restricted to
just one or two functions. Entry point for the CHIINV function would be
in sc/source/core/tool/interpr3.cxx ScInterpreter::ScChiInv()
If you want to get a working build without disabling all checks then you
can use
https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=b9a27d5856f60688456762bfcc29c38670009254

that disables the function tests for linux_x86 builds.

However, if you'd find a general solution that does not involve
disabling the tests that would be more than welcomed.

   Eike



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.