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


Hi all,

subsequentcheck for the gbuild modules is clean. Just type

  make -f GNUmakefile.mk -srkj30 gb_COLOR=t subsequentcheck

in the source root and be amazed by the blinkenlights(*). It should
complete without any errors or hickups.

The dirty secret is of course that I had to disable a few tests for
that. You will find a list of them here:

 https://bugs.freedesktop.org/buglist.cgi?cmdtype=runnamed&namedcmd=subsequenttests

So, if you are looking for a place to hack, these might be good
starting points as they show clearly reproducible bugs (and one of
them leads right into a crash).

The good thing about this is, as soon as there are errors popping up
when running subsequentcheck now, we know them to be regressions and
should take care of them!

Best Regards,

Bjoern

(*) Well, as said: you need to build smoketest before.

-- 
https://launchpad.net/~bjoern-michaelsen

Attachment: signature.asc
Description: PGP 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.