On Thu, 2010-10-28 at 13:21 +0100, Caolán McNamara wrote:
Hmm, sort of looks like the underlying cppu stuff, or something it uses,
got pulled out from under it during the test. I don't think it could
have gotten that far for the uno::sequence dtor (which looks up the type
of its argument) to
Caolan McNamara wrote:
register component 'configmgr.uno.so' in registry
'../../unxlngx6.pro/misc/qa_unit/services.rdb' failed!
error (CannotRegisterImplementationException): loading component library
failed: configmgr.uno.so
Can you (git pull bootstrap) and try export DEBUGREGCOMP=1
On Thu, 2010-10-28 at 11:17 +0200, Thorsten Behrens wrote:
Caolan McNamara wrote:
register component 'configmgr.uno.so' in registry
'../../unxlngx6.pro/misc/qa_unit/services.rdb' failed!
error (CannotRegisterImplementationException): loading component library
failed:
Michael Meeks wrote:
On Wed, 2010-10-27 at 01:15 +0200, Thorsten Behrens wrote:
I've for the while reverted the commit, will look into this tomorrow.
Ah ! - better to add a prefix to the prj/build.lst dep. or something to
the makefile.mk so it still build on (only) Linux (?) ;-)
On Mon, 2010-10-25 at 21:58 -0400, Kohei Yoshida wrote:
On Wed, 2010-10-20 at 20:44 +0100, Caolán McNamara wrote:
So the sc test, while working reliably for me, is apparently not
working for Kohei and others
So, I came home and did a clean re-build of the latest source tree on my
Caolan McNamara wrote:
Righteo, re-enabled again and lets have another go. Right away I see it
detected a new bug introduced with the vos removalstuff, which I've now
fixed :-). Tests are good.
Hi Caolan,
sorry - breaks for me on at least two platforms consistently. Error
log snippet:
rm -f
On Wed, 2010-10-20 at 20:44 +0100, Caolán McNamara wrote:
So the sc test, while working reliably for me, is apparently not
working for Kohei and others
So, I came home and did a clean re-build of the latest source tree on my
reasonably fast desktop machine, and the unit test now runs with
Caolan McNamara wrote:
sc/qa/unit had an existing cppunit test to ensure that calc can do
=SUM(A1:A2) correctly but it was currently disabled seeing as it didn't
work, mostly due to miserable bootstrapping problems. I've fixed that
test (I think), so I hope it can now provide a basis for