Searched refs:retry (Results 1 – 10 of 10) sorted by relevance
93 # primarily due to the AV retry delay being set to 1 millisecond in the95 # case for the AV retry logic, a failure of this test should probably not
63 # Sanity checking. Have [db] release the lock and then retry the
25 # lock) it should retry up to 100 times. Then return SQLITE_PROTOCOL to the
84 # retry the delete. The delete should work this time.
33 # lock) it should retry up to 100 times. Then return SQLITE_PROTOCOL to the
1227 # The error persist on retry when sqlite3_prepare() has been used.
205 Atomics.wait(state.sabOPView, state.opIds.retry, 0, ms);
307 state.opIds.retry = i++;
7437 int retry = 0; in win32_file_lock() local7451 while( x.h && retry<30 ){ in win32_file_lock()7452 retry++; in win32_file_lock()
940 ** retry counts and intervals for certain disk I/O operations for the942 ** anti-virus programs. By default, the windows VFS will retry file read,944 ** of 25 milliseconds before the first retry and with the delay increasing945 ** by an additional 25 milliseconds with each subsequent retry. This949 ** integers where the first integer is the new retry count and the second952 ** into the array entry, allowing the current retry settings to be4805 ** or occurs outside of an explicit transaction, then you can retry the