/ Check-in [2d896667]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Disable shared-cache OOM tests if not compiled with -DSQLITE_MEMDEBUG. (CVS 3016)
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 2d896667e460dcdaf83d18bd03050e917d54edc7
User & Date: drh 2006-01-23 23:49:34
Context
2006-01-23
23:53
Change the release date for version 3.3.2 to January 24. (CVS 3017) check-in: 7a2617f6 user: drh tags: trunk
23:49
Disable shared-cache OOM tests if not compiled with -DSQLITE_MEMDEBUG. (CVS 3016) check-in: 2d896667 user: drh tags: trunk
22:15
Bug fix in the WinCE bindings. (CVS 3015) check-in: c5792283 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to test/shared_err.test.

9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
...
264
265
266
267
268
269
270








271
272
273
274
275
276
277
...
322
323
324
325
326
327
328
329
#
#***********************************************************************
#
# The focus of the tests in this file are IO errors that occur in a shared
# 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.5 2006/01/23 13:09:47 danielk1977 Exp $

proc skip {args} {}


set testdir [file dirname $argv0]
source $testdir/tester.tcl
db close
................................................................................
  } {002.002.002.002.002}
  do_test shared_ioerr-3.$n.cleanup.3 {
    sqlite3_finalize $::STMT
  } {SQLITE_OK}
# db2 eval {select * from sqlite_master}
  db2 close
}









# Provoke a malloc() failure when a cursor position is being saved. This
# only happens with index cursors (because they malloc() space to save the
# current key value). It does not happen with tables, because an integer
# key does not require a malloc() to store. 
#
# The library should return an SQLITE_NOMEM to the caller. The query that
................................................................................
  catch {dbX close}
  catch {dbY close}
}

catch {db close}
sqlite3_enable_shared_cache $::enable_shared_cache
finish_test








|







 







>
>
>
>
>
>
>
>







 







<
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
...
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
...
330
331
332
333
334
335
336

#
#***********************************************************************
#
# The focus of the tests in this file are IO errors that occur in a shared
# 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.6 2006/01/23 23:49:34 drh Exp $

proc skip {args} {}


set testdir [file dirname $argv0]
source $testdir/tester.tcl
db close
................................................................................
  } {002.002.002.002.002}
  do_test shared_ioerr-3.$n.cleanup.3 {
    sqlite3_finalize $::STMT
  } {SQLITE_OK}
# db2 eval {select * from sqlite_master}
  db2 close
}

# Only run these tests if memory debugging is turned on.
#
if {[info command sqlite_malloc_stat]==""} {
   puts "Skipping malloc tests: not compiled with -DSQLITE_MEMDEBUG..."
   finish_test
   return
}

# Provoke a malloc() failure when a cursor position is being saved. This
# only happens with index cursors (because they malloc() space to save the
# current key value). It does not happen with tables, because an integer
# key does not require a malloc() to store. 
#
# The library should return an SQLITE_NOMEM to the caller. The query that
................................................................................
  catch {dbX close}
  catch {dbY close}
}

catch {db close}
sqlite3_enable_shared_cache $::enable_shared_cache
finish_test