database/sqlite
1
0
Fork 0
mirror of https://github.com/sqlite/sqlite.git synced 2025-07-27 20:41:58 +03:00
Code Activity

The shared_err test runs with no errors. But a potential deadlock has been

Browse Source 
discovered and is still unfixed. (CVS 4317)

FossilOrigin-Name: f84550be0a0c9e5859b852863b9a8f8ed3fd6919
This commit is contained in:
drh
2007-08-28 23:28:07 +00:00
parent d0679edc7a
commit 4cf7c7f7e7
9 changed files with 48 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
test/shared_err.test
View File

@ -13,7 +13,7 @@
# cache context. What happens to connection B if one connection A encounters
# an IO-error whilst reading or writing the file-system?
#
# $Id: shared_err.test,v 1.13 2007/08/28 22:24:35 drh Exp $
# $Id: shared_err.test,v 1.14 2007/08/28 23:28:09 drh Exp $
proc skip {args} {}
@ -156,7 +156,6 @@ do_ioerr_test shared_ioerr-3 -tclprep {
sqlite3_step $::STMT ;# Cursor points at 001.001.001.001
} -tclbody {
btree_breakpoint
execsql {
BEGIN;
INSERT INTO t1 VALUES('201.201.201.201.201', NULL);