mirror of
https://github.com/sqlite/sqlite.git
synced 2025-07-27 20:41:58 +03:00
Disable shared-cache OOM tests if not compiled with -DSQLITE_MEMDEBUG. (CVS 3016)
FossilOrigin-Name: 2d896667e460dcdaf83d18bd03050e917d54edc7
This commit is contained in:
@ -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.5 2006/01/23 13:09:47 danielk1977 Exp $
|
||||
# $Id: shared_err.test,v 1.6 2006/01/23 23:49:34 drh Exp $
|
||||
|
||||
proc skip {args} {}
|
||||
|
||||
@ -269,6 +269,14 @@ do_ioerr_test shared_ioerr-3 -tclprep {
|
||||
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
|
||||
@ -326,4 +334,3 @@ do_malloc_test 5 -tclbody {
|
||||
catch {db close}
|
||||
sqlite3_enable_shared_cache $::enable_shared_cache
|
||||
finish_test
|
||||
|
||||
|
Reference in New Issue
Block a user