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


Hi Markus,

On Tue, May 17, 2016 at 02:37:02AM +0200, Markus Mohrhard <markus.mohrhard@googlemail.com> wrote:
After that the results of a time make, therefore forcing the build of
everything test related and executing the tests:

real    11m30.192s
user    58m43.384s
sys    1m36.876s

And finally a second time make to measure the time it takes to just execute
the tests:

real    6m37.479s
user    45m4.740s
sys    0m34.988s

Is this just toplevel 'make' or 'make check'? I find it a bit strange
that we have 'make build-nocheck' to build the code, 'make check' to run
the tests, and 'make' to do something between the two -- and this
"something" is the default. ;-)

Also, I didn't do measurements, but my impression is that the current
hot path in 'make check' are still the Java tests, so if we want faster
'make check', then perhaps a way towards that would be to accelerate the
conversion of the majority of those Java tests to in-process ones.

Or did I miss something? :-)

Regards,

Miklos

Attachment: signature.asc
Description: Digital signature


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.