From 963048332bf135457ca163dc339579d0a710a26e Mon Sep 17 00:00:00 2001 From: Olly Betts Date: Wed, 4 Apr 2018 08:43:12 +1200 Subject: [PATCH] Enable testcase closedb5 for remote backends This testcase failed for remote backends when it was added and the cause wasn't clear, but it turns out it was actually a bug in the disk based backends, which was already fixed back in 2010 by 9cf77da645325affb88fac71760add8f4a9088a9. Reported by Guruprasad Hegde. --- xapian-core/tests/api_closedb.cc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/xapian-core/tests/api_closedb.cc b/xapian-core/tests/api_closedb.cc index 4d4c7f06c..8fa482980 100644 --- a/xapian-core/tests/api_closedb.cc +++ b/xapian-core/tests/api_closedb.cc @@ -221,9 +221,7 @@ DEFINE_TESTCASE(closedb4, writable && !inmemory) { } /// If a transaction is active, close() shouldn't implicitly commit(). -DEFINE_TESTCASE(closedb5, transactions && !remote) { - // FIXME: Fails with the remote backend, but I suspect it may be a test - // harness issue. +DEFINE_TESTCASE(closedb5, transactions) { { Xapian::WritableDatabase wdb = get_writable_database(); wdb.begin_transaction(); -- 2.11.4.GIT