Searched refs:failure (Results 1 – 25 of 57) sorted by relevance
123
| /sqlite-3.40.0/test/ |
| H A D | mallocC.test | 12 # This file tests aspects of the malloc failure while parsing 35 # Run the SQL. Malloc number $::n is set to fail. A malloc() failure 58 # Recover from the malloc failure. 60 # Update: The new malloc() failure handling means that a transaction may
|
| H A D | oserror.test | 47 # Test a failure in open() due to too many files. 84 # Test a failure in open() due to the path being a directory. 94 # Test a failure in open() due to the path not existing. 103 # Test a failure in open() due to the path not existing.
|
| H A D | mallocI.test | 29 # Malloc failure while trying to service a pragma on a TEMP database. 35 # Malloc failure while creating a table from a SELECT statement. 43 # This tests that a malloc failure that occurs while passing the schema
|
| H A D | malloc.test | 212 # occur in vdbeapi.c. Specifically, if a malloc failure that occurs 497 # Make sure SQLITE_NOMEM is reported out on an ATTACH failure even 498 # when the malloc failure occurs within the nested parse. 520 # Test malloc failure whilst installing a foreign key. 528 # Test malloc failure in an sqlite3_prepare_v2() call. 623 # aimed at testing the response of the library to a failure in that 635 # failure while seeking to the right-hand side of the B-Tree to insert 653 # Test that no memory is leaked following a malloc() failure in 730 # If, when running in exclusive mode, a malloc() failure occurs 736 # the malloc failure and rollback, the change counter will not [all …]
|
| H A D | malloc4.test | 20 # [193] When a memory allocation failure occurs during sqlite3_column_name(), 57 # Test malloc failure in the _name(), _name16(), decltype() and 58 # decltype16() APIs. Calls that occur after the malloc() failure should
|
| H A D | bitvec.test | 154 # "failcnt"-th malloc. The result should be "0" if no malloc failure 155 # occurs or "-1" if there is a malloc failure.
|
| H A D | crash5.test | 13 # This file tests aspects of recovery from a malloc() failure 84 # failure occurred in the OS layer), write to the database. Make sure
|
| H A D | malloc3.test | 71 # malloc() failure may occur within any stage. If a memory allocation fails 92 # in the same way as a failure within _finalize(). The statement handle 100 # The effect of a malloc failure on concurrently executing SQL statements, 102 # the malloc() failure mandates statement rollback only. Currently, if 241 # (and hence after each failure of the first insert), and that it has been 625 error "Unreported malloc() failure, test \"$testid\", $expr"
|
| H A D | trans2.test | 155 # Do a large update that aborts do to a constraint failure near 179 # Do another large update that aborts do to a constraint failure near
|
| H A D | tkt3929.test | 43 # assertion failure or a "database is malformed" error.
|
| H A D | init.test | 13 # focus of this file is testing the effects of a failure in
|
| H A D | mallocB.test | 40 # malloc() failure in sqlite3_set_auxdata().
|
| H A D | mallocH.test | 62 # Malloc failure during integrity_check pragma.
|
| H A D | altermalloc.test | 45 # Test malloc() failure on an ALTER TABLE on a virtual table.
|
| H A D | shared_err.test | 303 # Provoke a malloc() failure when a cursor position is being saved. This 383 # Again provoke a malloc() failure when a cursor position is being saved, 455 # Test that one or more queries were aborted due to the malloc() failure.
|
| H A D | in2.test | 53 # during b-tree balancing was causing an assertion failure.
|
| H A D | fuzz_malloc.test | 76 # Test malloc failure during parsing (and execution) of a fuzzily
|
| H A D | collateB.test | 65 # Test an assert() failure that was occuring if an index were created
|
| H A D | fts2g.test | 88 # row, and when combined there was an assertion failure.
|
| H A D | fts3ag.test | 88 # row, and when combined there was an assertion failure.
|
| H A D | json103.test | 61 # The underlying problem is a failure to reset Mem.eSubtype
|
| H A D | auth3.test | 115 # an authorizer failure during an ALTER TABLE. The solution (I think) is
|
| H A D | crash.test | 15 # from a power failure during the middle of a COMMIT. The OS interface 18 # occurs after a power failure.
|
| /sqlite-3.40.0/ext/lsm1/lsm-test/ |
| H A D | README | 28 live-recovery (recovery from a failure that occurs while other 30 from a system or power failure.
|
| /sqlite-3.40.0/doc/ |
| H A D | F2FS.txt | 76 to persistent storage before the failure occurred.
|
123