Import SQLite 3.8.7.4.

third_party/sqlite/src/test/tkt3793.test

 # 2009 April 10
 #
 # The author disclaims copyright to this source code.  In place of
 # a legal notice, here is a blessing:
 #
 #    May you do good and not evil.
 #    May you find forgiveness for yourself and forgive others.
 #    May you share freely, never taking more than you give.
 #
 #***********************************************************************
@@ skipping 82 matching lines @@
 # SQLite will attempt to upgrade to an EXCLUSIVE lock, and hence invoke
 # the busy-handler. The tests here verify that the correct busy-handler
 # function is invoked (the busy-handler associated with the database
 # connection that called sqlite3_step()). When bug #3793 existed, sometimes
 # the [db2] busy-handler was invoked from within the call to sqlite3_step()
 # associated with [db1]. 
 #
 # Note: Before the bug was fixed, if [db2] was opened with the "-fullmutex 1"
 # option, then this test case would cause an assert() to fail.
 #
-set ::busyconnection db1
-db1 eval {SELECT * FROM t2 ORDER BY a LIMIT 20} {
-  do_test tkt3793-2.[incr x] { set ::busyconnection } db1
-  set ::busyconnection db2
-
-  db2 eval { SELECT count(*) FROM t2 }
-  do_test tkt3793-2.[incr x] { set ::busyconnection } db2
+ifcapable threadsafe {
   set ::busyconnection db1
+  db1 eval {SELECT * FROM t2 ORDER BY a LIMIT 20} {
+    do_test tkt3793-2.[incr x] { set ::busyconnection } db1
+    set ::busyconnection db2
+  
+    db2 eval { SELECT count(*) FROM t2 }
+    do_test tkt3793-2.[incr x] { set ::busyconnection } db2
+    set ::busyconnection db1
+  }
 }
-
+  
 do_test tkt3793-3 {
   db1 close
   db2 close
 } {}
 
 sqlite3_enable_shared_cache $::enable_shared_cache
 finish_test