Home
last modified time | relevance | path

Searched refs:fail (Results 1 – 25 of 112) sorted by relevance

12345

/sqlite-3.40.0/vsixtest/
H A Dvsixtest.tcl37 proc fail { {error ""} {usage false} } { procedure
201 fail "this tool only works properly on Windows"
209 set argc [llength $argv]; if {$argc > 1} then {fail "" true}
221 fail [appendArgs \
228 fail [appendArgs \
235 fail [appendArgs \
244 fail [appendArgs \
254 fail [appendArgs \
263 fail [appendArgs \
272 fail [appendArgs \
[all …]
/sqlite-3.40.0/tool/
H A Dmkvsix.tcl98 proc fail { {error ""} {usage false} } { procedure
310 if {$argc < 1 || $argc > 5} then {fail}
315 fail "invalid binary directory"
334 fail "invalid source directory"
352 fail "invalid package flavor"
374 fail "invalid Visual Studio version"
379 fail [appendArgs \
417 fail [appendArgs \
444 fail [appendArgs \
460 fail [appendArgs \
[all …]
/sqlite-3.40.0/test/
H A Dfts4check.test45 # this causes the integrity-check code to fail.
54 # integrity-check test to fail.
89 # this causes the integrity-check code to fail.
123 # this causes the integrity-check code to fail.
H A Dmalloc4.test54 # Set the Nth malloc() to fail.
103 # running sqlite3_step(), make sure that malloc() is not about to fail.
165 # SQLITE_ERROR. If malloc() did not fail, it should return SQLITE_DONE.
H A Dtkt2820.test14 # occurs while a query is in process will fail with a
81 # The INSERT statement within the loop should fail on a
H A Dsavepointfault.test82 # operation in pagerPlaybackSavepoint() to fail.
109 # Cause a specific malloc in savepoint rollback code to fail.
H A Doserror.test51 # a call to getcwd() may fail if there are no free file descriptors. So
65 # such systems will not fail here
H A Ddelete2.test23 # Step 3 will fail because there is still a read cursor on the table.
69 # As of 2006-08-16, this is allowed. (It used to fail with SQLITE_LOCKED.)
H A Dtrigger3.test36 WHEN (new.a = 2) THEN RAISE(FAIL, 'Trigger fail')
66 } {1 {Trigger fail}}
H A Dcrash5.test67 # with the iFail'th malloc() set to fail. This operation will
80 # puts "fail=[sqlite3_memdebug_fail -1]"
H A DcorruptF.test84 # At one point this was causing an assert to fail.
97 # its iteration, which causes an assert() to fail.
H A Dioerr2.test117 # fail with "abort due to ROLLBACK". Now, the loop continues until the UPDATE
143 # determine if the specified directory is writable to fail. This causes
H A DcorruptI.test195 # point this led to an integer overflow that caused an assert() to fail.
237 # At one point an assert() would fail if attempt was made to free page 1.
H A Dfkey4.test16 # a subsequent statement to fail a deferred constraint with impunity.
H A Dmutex2.test49 # require that SQLite be initialized. Verify that they fail.
H A Dfuzz.test99 # to fail. Probably harmless.
290 # At one point the following INSERT statement caused an assert() to fail.
H A Dsharedlock.test42 # This should fail. Connection [db] has a read-lock on t1, which should
H A Dioerr6.test47 # Cause the first call to xWrite() to fail with SQLITE_FULL.
H A Dvacuummem.test32 # causing tests in this file to fail.
H A Dkeyword1.test51 fail
H A Dtkt-313723c356.test47 # the integrity-check in the "-test" code to fail, as it is comparing the
H A Dtkt3093.test50 # busy handler is called a second time, then fail so that we get
H A Dmalloc.test15 # which causes the N-th malloc to fail. This special feature is used
16 # to see what happens in the library if a malloc were to really fail
469 # encodings to fail (i.e. little-endian->big-endian). It only actually
788 # the database file, the integrity check should fail.
832 # At one point an assert( !db->mallocFailed ) could fail in the following
H A DtriggerG.test65 # At one point the following was causing an assert() to fail.
/sqlite-3.40.0/ext/wasm/common/
H A Dtesting.css41 .tests-fail { background-color: red; color: yellow }

12345