On Mon, Jun 01, 2015 at 09:23:42AM +0200, Miklos Vajna wrote:
On Sat, May 30, 2015 at 08:34:13AM -0700, Lionel Elie Mamane <lionel@mamane.lu> wrote:
New commits:
commit 9b06d36571bbfa2d722f36610375e7cd24be81a7
Author: Lionel Elie Mamane <lionel@mamane.lu>
Date: Sat May 30 17:08:49 2015 +0200
reenable JunitTest_dbaccess_complex part RowSet
Change-Id: I82a1af0cd6b068e9f349ec6b068e78d55e8ab969
diff --git a/dbaccess/JunitTest_dbaccess_complex.mk b/dbaccess/JunitTest_dbaccess_complex.mk
index e3f2c00..7a0b17b 100644
--- a/dbaccess/JunitTest_dbaccess_complex.mk
+++ b/dbaccess/JunitTest_dbaccess_complex.mk
@@ -27,6 +27,7 @@ $(eval $(call gb_JunitTest_set_defs,dbaccess_complex,\
$(eval $(call gb_JunitTest_add_classes,dbaccess_complex,\
complex.dbaccess.Beamer \
complex.dbaccess.PropertyBag \
+ complex.dbaccess.RowSet \
))
This last commit makes 'make check' fail debug-enabled Linux builds at
least, see
<http://ci.libreoffice.org/job/lo_tb_master_linux_dbg/622/console>, I
also got that locally.
For now, I just re-disabled the RowSet part on master, please if you
would enable it again, first make sure that a debug 'make check' is
happy before pushing. :-)
Interesting... I got that error on my machine, I made some changes,
and then didn't get it on three consecutive "make JunitTest_dbaccess_complex"
so I thought it gone. The operative part is
Caught UNO exception 'URP: queryInterface request message with unknown OID received'
Anybody has a clue what this is about?
--
Lionel
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.