On Mon, 2013-02-18 at 19:27 +0100, Markus Mohrhard wrote:
Currently I plan to run the script every 2 or 3 weeks on a TDF server
and report the documents back. Hopefully some of these tasks can be
automated by time and we only need someone to start the build. There
are several open tasks and some things I noticed would be nice to
have. I list them here to make is easier for others to step in and
implement some of them or add their own ideas:
Great. Some thoughts...
a) TODO: repeat failed, or maybe newly failed, or a tiny subset of those
with VALGRIND=memcheck to get some info on their failure
b) What to do with the super super slow ones, e.g.
https://bugs.freedesktop.org/show_bug.cgi?id=45820
might need to blacklist a few docs that takes hours, or preferably fix
that one :-)
Was there also a "cunning plan" wrt callgrind runs to get some form of
performance-regression testing in the works ?
C.
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.