2013/2/18 Caolán McNamara <caol...@redhat.com>: > 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
Good idea. Thanks. > 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 :-) Sorry forgot to mention in the original mail. I already implemented a timeout as I would not have executed it without some sort of safety net on a server. Currently the sccript generates 3 files: good files, bad files and files where we were too slow. These documents either need manual checks or can be used as cases for further performance improvements. > > Was there also a "cunning plan" wrt callgrind runs to get some form of > performance-regression testing in the works ? > I think Norbert plans to use the same server for some performance tests but I'm unaware how far he is already with this plan. A TODO that I forgot in my initial list is that we need an incremental option for the get-bugzilla-attachments script. The integration of the bugzilla-attachment script would be the final step in making these test truely automatic. Regards, Markus _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
