search for: topercent2

> Is that the complete output? Yes it is the complete output against "./runtest ./apitest --verbose topercent2"( after running make remove-cached-databases). I attached the snapshot of the output of commands but the size of the email got bigger than 40kb so i had to place the output as text. If I do not run "make remove-cached-databases" and run "./runtest ./apitest --verbose topercent2...

...ng for reply regarding any further steps to take. Following are the outputs of commands that you asked me to run. All these commands were executed in order. Commands: make remove-cached-databases rm -rf .chert .glass .multichert .multiglass .replicatmp .stub Command:./runtest ./apitest --verbose topercent2 Output: Running test './apitest --verbose topercent2' under eatmydata and valgrind Running tests with backend "none"... Running tests with backend "inmemory"... Running test: topercent2... Command: ls -R .chert Output: .chert: db=apitest_simpledata .chert/db=apitest_si...

...uccessfully build the code. But when I run the > > existing testcases (to verify everthing is working fine), It says 3 out > of > > the six testcases fails. Here is the report of the test cases. > > > Running tests with backend "inmemory"... > > Running test: topercent2...FAIL: apitest > > > Running test './queryparsertest' under eatmydata and valgrind > > Running test: qp_spell1...FAIL: queryparsertest > > > Running test './termgentest' under eatmydata and valgrind > > Running test: tg_spell1...FAIL: termgentest >...

...Entering directory `/home/saad/GitProjects/xapian/build/xapian-core/tests' Running test './apitest' under eatmydata and valgrind Running tests with backend "none"... ./apitest backend none: All 85 tests passed. Running tests with backend "inmemory"... Running test: topercent2...FAIL: apitest Running test './internaltest' under eatmydata and valgrind PASS: internaltest Running test './stemtest' under eatmydata and valgrind The random seed is 42 Please report the seed when reporting a test failure. Running tests with armenian stemmer... Running test: ste...

...runs "make > distcheck", which runs the testsuite, so these tests didn't fail for me > when I made the 1.3.2 release. > > When I run "make distcheck" in the "build" folder, it gives the same output as given in above log. (i.e. 3 out 6 tests fail) > topercent2 opens a local disk-based database as well as the one of the > backend type requested, so it can check the same results are given. > It must be the disk-based database which fails, but I can't see why. > > I suspect you've ended up with a corrupt cached database, and this > ex...

...ning test: expandweights4... FAILED Running test: msetweights1... FAILED Running test: netstats1... FAILED Running test: pctcutoff2... FAILED Running test: rsetmultidb2... FAILED Running test: scaleweight1... FAILED Running test: simplequery2... FAILED Running test: sortrel1... FAILED Running test: topercent2... FAILED Running test: topercent4... FAILED Running test: topercent5... FAILED Running test: valuestats3... FAILED Running test: valueweightsource1... FAILED Running test: valueweightsource2... FAILED Running test: weight1... FAILED Running test: wqf1... FAILED Running test: xor3... FAILED Runnin...