Hi Bjoern,
On Fri, 2011-03-25 at 17:37 +0100, Bjoern Michaelsen wrote:
> subsequentcheck for the gbuild modules is clean. Just type
Ooh - fun :-)
> 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.
I guess we should add this to the end of the generic all: rule for
compilation, as we should with the smoketest IMHO (at least for Linux
where it runs headless).
Having said that - it is somewhat annoying all of the graphical thrash
that this introduces: I end up with lots of flickering windows, and some
seem to just hang there ;-) Did I really break -headless somehow with
the new oostart.bin ? [ it works when I try it manually ], and/or do we
need to tweak the tests so they pass that ?
> 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).
Ooh ! nice - can you add that to the easy hacks ? and we also have a
3.4 blocker bug here: https://bugs.freedesktop.org/show_bug.cgi?id=35673
that might be nice to have those tracked on.
> 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!
Right. The only problem is the graphical thrash I guess.
Anyhow - great to see this in-place.
Thanks,
Michael.
--
michael.me...@novell.com <><, Pseudo Engineer, itinerant idiot
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
