Opened 16 years ago
Closed 15 years ago
#312 closed defect (fixed)
Test failures with backend "remotetcp_chert"
Reported by: | Charlie Hull | Owned by: | Olly Betts |
---|---|---|---|
Priority: | normal | Milestone: | 1.1.2 |
Component: | Backend-Chert | Version: | SVN trunk |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Operating System: | Microsoft Windows |
Description (last modified by )
Multiple failures as follows (this is tidied version of the log output):
apitest.exe Running tests with backend "remotetcp_chert"... Running test: valueweightsource3... NetworkErrorNetworkError: read failed (context: remote:tcp(127.0.0.1:1241)) (Reached the end of the file.) Running test: netstats1... NetworkErrorNetworkError: Handshake failed - is this a Xapian server? (context: remote:tcp(127.0.0.1:1242)) Running test: externalsource2... NetworkErrorNetworkError: Handshake failed - is this a Xapian server? (context: remote:tcp(127.0.0.1:1243)) Running test: badtransaction1... NetworkErrorNetworkError: Handshake failed - is this a Xapian server? (context: remote:tcp(127.0.0.1:1244)) Running test: committransaction1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: canceltransaction1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: canceltransaction2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc3... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc4... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc5... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc6... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: implicitendsession1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: databaseassign1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc3... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc4... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc5... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc6... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc3... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc4... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc5... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc6... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: uniqueterm1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: allpostlist2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: emptyterm2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: phraseorneartoand1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: longpositionlist1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: nomoredocids1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: metadata1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: termtoolong1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: postlist7... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: bigoaddvalue... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: modifyvalues1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw
Attachments (1)
Change History (10)
comment:1 by , 16 years ago
Description: | modified (diff) |
---|
comment:2 by , 16 years ago
In what way is this tidied? Did some of the tests pass, and you've removed those lines?
comment:3 by , 16 years ago
yes, I just pasted in the tests that failed. Not that tidy really, better now you've done it!!
comment:4 by , 16 years ago
Slight difference after applying the latest patch for #303, not sure if it's anything to do with that:
Running tests with backend "remotetcp_chert"... Running test: valueweightsource2... ok Running test: valueweightsource3... ok Running test: valuerange2... ok Running test: alldocspl1... ok Running test: alldocspl2... ok Running test: near1... ok Running test: near2... ok Running test: phrase1... ok Running test: phrase2... NetworkErrorNetworkError: Handshake failed - is this a Xapian server? (context: remote:tcp(127.0.0.1:1241)) Running test: poslist1... NetworkErrorNetworkError: Handshake failed - is this a Xapian server? (context: remote:tcp(127.0.0.1:1242)) Running test: positfromtermit1... NetworkErrorNetworkError: Handshake failed - is this a Xapian server? (context: remote:tcp(127.0.0.1:1243)) Running test: poslist2... NetworkErrorNetworkError: Handshake failed - is this a Xapian server? (context: remote:tcp(127.0.0.1:1244)) Running test: poslist3... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: keepalive1... NetworkErrorNetworkError: Handshake failed - is this a Xapian server? (context: remote:tcp(127.0.0.1:1245)) Running test: netstats1... ok Running test: externalsource2... ok Running test: badtransaction1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: committransaction1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: canceltransaction1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: canceltransaction2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc3... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc4... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc5... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: adddoc6... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: implicitendsession1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: databaseassign1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc3... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc4... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc5... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: deldoc6... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc3... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc4... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc5... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: replacedoc6... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: uniqueterm1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: allpostlist2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: emptyterm2... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: phraseorneartoand1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: longpositionlist1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: crashrecovery1... Test only supported for flint and chert backends SKIPPED Running test: nomoredocids1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: metadata1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: termtoolong1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: postlist7... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: bigoaddvalue... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw Running test: modifyvalues1... DatabaseLockErrorDatabaseLockError: Unable to acquire database write lock on .chert/dbw .\apitest.EXE backend remotetcp_chert: 114 tests passed, 41 failed, 2 skipped.
comment:5 by , 16 years ago
FWIW, I think I'd prefer untrimmed output as an attachment in future. So often people trimming output remove something important without realising it, and it's not so easy to read pasted into the bug report directly either.
I'm wondering if you might have a stuck xapian-tcpsrv running on one of the databases. Have you rebooted recently? If not, look in the process list for any xapian-tcpsrv (or xapian-progsrv) processes and kill them off.
If not, have you tried deleting the cached test databases in .chert? The valuestream stuff changed the format (though I can't see why that would give this particular error).
comment:6 by , 16 years ago
Just re-tested after a clean reboot, and verified that 'nmake clean' actually does clean up all the .xxx test databases. Re-running the tests produces the same result as above. However I've noticed some additional errors of the form:
.chert\dbw\chertlock - The process cannot access the file because it is being us ed by another process.
(these were going to stderr and thus weren't being captured by a stdout redirect, sorry) Attaching a file with a complete log.
comment:7 by , 15 years ago
Milestone: | → 1.1.7 |
---|
Is this still manifesting with current trunk? A lot has changed in the last year - particularly notable being that we now wait for remote server processes to exit in the test harness.
Setting milestone:1.1.7 to keep this on the radar - if this can easily be fixed we should do so (if it isn't already fixed), though I don't think it is a release blocker unless there's evidence we can't fix it without breaking ABI (I would be very surprised if that was an issue).
comment:9 by , 15 years ago
Milestone: | 1.1.7 → 1.1.2 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Marking as fixed in 1.1.2, which is my best guess.
Quoted the output with { { { and } } } so I can read it.