Hi,
On Tue, May 17, 2016 at 09:31:54AM +0200, Miklos Vajna wrote:
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.
since Markus said he ran "make" (not "make check") twice, none of the above
number include anything Java-ish (those are in "make check" and "make
subsequentcheck" but not in "make" or "make slowcheck unitcheck"). So, if
anything, these numbers show that the non-Java tests grow and will dominate
even "make check" soon.
Best,
Bjoern
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.