Vasiliy Sergeev
2007-Dec-04 10:45 UTC
[Xapian-discuss] errors with flint database, xapian 1.0.4
Hello everyone! I have met a problem with installation of xapian 1.0.4 on RHEL4 x86_64 ( kernel is 2.6.9). I attached test log for xapian-core. It seems all errors occur with flint database and remotetcp tests. I used flint database in xapian 0.9.10 and they worked fine. Please advise, Thanks. Vaso. -------------- next part -------------- make check-TESTS make[3]: Entering directory `/root/xapian-core-1.0.4/tests' Running test './btreetest' under valgrind ./btreetest completed test run: All 15 tests passed. PASS: btreetest Running test './quartztest' under valgrind ./quartztest completed test run: All 10 tests passed. PASS: quartztest Running test './apitest' under valgrind Running nodb tests with none backend... ./apitest completed test run: All 19 tests passed. Running unicode tests with none backend... ./apitest completed test run: All 3 tests passed. Running anydb tests with inmemory backend... ./apitest completed test run: All 63 tests passed. Running specchar tests with inmemory backend... ./apitest completed test run: All 1 tests passed. Running writabledb tests with inmemory backend... Running test: crashrecovery1... SKIPPED Running test: nomoredocids1... SKIPPED Running test: spell1... SKIPPED Running test: spell2... SKIPPED Running test: spell3... SKIPPED Running test: spell4... SKIPPED Running test: spell5... SKIPPED Running test: synonymitor1... SKIPPED Running test: metadata2... SKIPPED Running test: termtoolong1... SKIPPED ./apitest completed test run: All 26 tests passed, 10 skipped. Running localdb tests with inmemory backend... ./apitest completed test run: All 19 tests passed. Running positionaldb tests with inmemory backend... ./apitest completed test run: All 8 tests passed. Running doclendb tests with inmemory backend... ./apitest completed test run: All 1 tests passed. Running collfreq tests with inmemory backend... ./apitest completed test run: All 1 tests passed. Running allterms tests with inmemory backend... ./apitest completed test run: All 7 tests passed. Running multivalue tests with inmemory backend... ./apitest completed test run: All 3 tests passed. Running anydb tests with flint backend... Running test: zerodocid1... =24029=Running test: puncterms1... =24029=Running test: checkatleast3... =24029=Running test: valuerange1... VALGRIND DETECTED A PROBLEM ./apitest completed test run: 59 tests passed, 4 failed. Running specchar tests with flint backend... ./apitest completed test run: All 1 tests passed. Running writabledb tests with flint backend... Running test: adddoc4... VALGRIND DETECTED A PROBLEM Running test: emptyterm2... VALGRIND DETECTED A PROBLEM ./apitest completed test run: 34 tests passed, 2 failed. Running localdb tests with flint backend... ./apitest completed test run: All 19 tests passed. Running positionaldb tests with flint backend... ./apitest completed test run: All 8 tests passed. Running doclendb tests with flint backend... ./apitest completed test run: All 1 tests passed. Running collfreq tests with flint backend... ./apitest completed test run: All 1 tests passed. Running allterms tests with flint backend... ./apitest completed test run: All 7 tests passed. Running multivalue tests with flint backend... ./apitest completed test run: All 3 tests passed. Running transactiondb tests with flint backend... ./apitest completed test run: All 4 tests passed. Running flint tests with flint backend... Running test: sortrel1... VALGRIND DETECTED A PROBLEM ./apitest completed test run: 7 tests passed, 1 failed. Running anydb tests with quartz backend... ./apitest completed test run: All 63 tests passed. Running specchar tests with quartz backend... ./apitest completed test run: All 1 tests passed. Running writabledb tests with quartz backend... Running test: spell1... SKIPPED Running test: spell2... SKIPPED Running test: spell3... SKIPPED Running test: spell4... SKIPPED Running test: spell5... SKIPPED Running test: synonymitor1... SKIPPED Running test: metadata1... SKIPPED Running test: metadata2... SKIPPED Running test: termtoolong1... SKIPPED ./apitest completed test run: All 27 tests passed, 9 skipped. Running localdb tests with quartz backend... ./apitest completed test run: All 19 tests passed. Running positionaldb tests with quartz backend... Running test: positfromtermit1... SKIPPED ./apitest completed test run: All 7 tests passed, 1 skipped. Running doclendb tests with quartz backend... ./apitest completed test run: All 1 tests passed. Running collfreq tests with quartz backend... ./apitest completed test run: All 1 tests passed. Running allterms tests with quartz backend... ./apitest completed test run: All 7 tests passed. Running multivalue tests with quartz backend... ./apitest completed test run: All 3 tests passed. Running transactiondb tests with quartz backend... ./apitest completed test run: All 4 tests passed. Running quartz tests with quartz backend... ./apitest completed test run: All 3 tests passed. Running anydb tests with remoteprog backend... ./apitest completed test run: All 63 tests passed. Running specchar tests with remoteprog backend... ./apitest completed test run: All 1 tests passed. Running writabledb tests with remoteprog backend... Running test: emptyterm2... VALGRIND DETECTED A PROBLEM Running test: crashrecovery1... SKIPPED Running test: spell1... SKIPPED Running test: spell2... SKIPPED Running test: spell3... SKIPPED Running test: spell4... SKIPPED Running test: spell5... SKIPPED Running test: synonymitor1... SKIPPED Running test: metadata1... SKIPPED Running test: metadata2... SKIPPED ./apitest completed test run: 26 tests passed, 1 failed, 9 skipped. Running remotedb tests with remoteprog backend... ./apitest completed test run: All 19 tests passed. Running positionaldb tests with remoteprog backend... Running test: near1... VALGRIND DETECTED A PROBLEM Running test: positfromtermit1... SKIPPED ./apitest completed test run: 6 tests passed, 1 failed, 1 skipped. Running doclendb tests with remoteprog backend... ./apitest completed test run: All 1 tests passed. Running collfreq tests with remoteprog backend... ./apitest completed test run: All 1 tests passed. Running allterms tests with remoteprog backend... ./apitest completed test run: All 7 tests passed. Running multivalue tests with remoteprog backend... ./apitest completed test run: All 3 tests passed. Running transactiondb tests with remoteprog backend... ./apitest completed test run: All 4 tests passed. Running anydb tests with remotetcp backend... Running test: zerodocid1... VALGRIND DETECTED A PROBLEM Running test: puncterms1... VALGRIND DETECTED A PROBLEM Running test: checkatleast3... VALGRIND DETECTED A PROBLEM ./apitest completed test run: 60 tests passed, 3 failed. Running specchar tests with remotetcp backend... ./apitest completed test run: All 1 tests passed. Running writabledb tests with remotetcp backend... Running test: emptyterm2... VALGRIND DETECTED A PROBLEM Running test: crashrecovery1... SKIPPED Running test: spell1... SKIPPED Running test: spell2... SKIPPED Running test: spell3... SKIPPED Running test: spell4... SKIPPED Running test: spell5... SKIPPED Running test: synonymitor1... SKIPPED Running test: metadata1... SKIPPED Running test: metadata2... SKIPPED ./apitest completed test run: 26 tests passed, 1 failed, 9 skipped. Running remotedb tests with remotetcp backend... Running test: sortrel1... VALGRIND DETECTED A PROBLEM ./apitest completed test run: 18 tests passed, 1 failed. Running positionaldb tests with remotetcp backend... Running test: near1... VALGRIND DETECTED A PROBLEM Running test: positfromtermit1... SKIPPED ./apitest completed test run: 6 tests passed, 1 failed, 1 skipped. Running doclendb tests with remotetcp backend... ./apitest completed test run: All 1 tests passed. Running collfreq tests with remotetcp backend... ./apitest completed test run: All 1 tests passed. Running allterms tests with remotetcp backend... ./apitest completed test run: All 7 tests passed. Running multivalue tests with remotetcp backend... ./apitest completed test run: All 3 tests passed. Running transactiondb tests with remotetcp backend... ./apitest completed test run: All 4 tests passed. ./apitest total: 689 tests passed, 15 failed, 40 skipped. FAIL: apitest Running test './internaltest' under valgrind ./internaltest completed test run: All 15 tests passed. PASS: internaltest Running test './stemtest' under valgrind The random seed is 42 Please report the seed when reporting a test failure. Running tests with danish stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with dutch stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with english stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with finnish stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with french stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with german stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with german2 stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with hungarian stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with italian stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with kraaij_pohlmann stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with lovins stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with norwegian stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with porter stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with portuguese stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with romanian stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with russian stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with spanish stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with swedish stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. Running tests with turkish stemmer... Running test: stemdict... SKIPPED ./stemtest completed test run: All 2 tests passed, 1 skipped. ./stemtest total: All 38 tests passed, 19 skipped. PASS: stemtest Running test './queryparsertest' under valgrind ./queryparsertest completed test run: All 25 tests passed. PASS: queryparsertest Running test './termgentest' under valgrind Running test: tg_spell1... =25762=./termgentest completed test run: 1 tests passed, 1 failed. FAIL: termgentest ==================2 of 7 tests failed ===================
Richard Boulton
2007-Dec-04 14:45 UTC
[Xapian-discuss] errors with flint database, xapian 1.0.4
Vasiliy Sergeev wrote:> Hello everyone! > I have met a problem with installation of xapian 1.0.4 on RHEL4 x86_64 ( > kernel is 2.6.9). > I attached test log for xapian-core. > It seems all errors occur with flint database and remotetcp tests. I > used flint database in xapian 0.9.10 and they worked fine. > Please advise, > Thanks.Could you test with a recent SVN snapshot? (From http://www.oligarchy.co.uk/xapian/trunk/ ) There have been various fixes since 1.0.4 - in particular, we're using an updated valgrind suppressions file to remove some incorrect error reports from valgrind on 64 bit hosts. If the errors still occur with a snapshot, though, we'd like to know so that we can fix them before the 1.0.5 release (which should be pretty soon now). -- Richard