Searched refs:seconds (Results 1 – 25 of 30) sorted by relevance
12
| /sqlite-3.40.0/test/ |
| H A D | walthread.test | 28 unset -nocomplain seconds 70 # -seconds SECONDS How many seconds to run the test for 81 set P(seconds) 5 95 -seconds { 129 puts "Running $P(testname) for $P(seconds) seconds..." 147 set E(seconds) $P(seconds) 247 do_thread_test2 walthread-1 -seconds $seconds(walthread-1) -init { 331 do_thread_test2 walthread-2 -seconds $seconds(walthread-2) -init { 387 do_thread_test walthread-3 -seconds $seconds(walthread-3) -init { 442 do_thread_test2 walthread-4 -seconds $seconds(walthread-4) -init { [all …]
|
| H A D | wapptest.tcl | 235 proc format_seconds {seconds} { argument 236 set min [format %.2d [expr ($seconds / 60) % 60]] 237 set hr [format %.2d [expr $seconds / 3600]] 238 set sec [format %.2d [expr $seconds % 60]] 248 set G(test.$name.done) [clock seconds] 421 set G(test.$name.start) [clock seconds] 545 set seconds "" 550 set seconds [expr [clock seconds] - $G(test.$config.start)] 557 set seconds [expr $G(test.$config.done) - $G(test.$config.start)] 559 set seconds [format_seconds $seconds] [all …]
|
| H A D | date.test | 121 datetest 2.28 {datetime('2003-10-22 12:34','11.25 seconds')} \ 137 datetest 2.41 {datetime('2003-10-22 12:24','23 seconds')} {2003-10-22 12:24:23} 143 datetest 2.47 {datetime('2003-10-22 12:24','8.6 seconds')} {2003-10-22 12:24:08} 349 datetest 8.19 {datetime('now','11.25 seconds')} {2003-10-22 12:34:11} 425 datetest 13.19 {julianday(2454832.5,'-675 seconds')} {2454832.4921875} 426 datetest 13.20 {julianday(2454832.5,'+675 seconds')} {2454832.5078125} 503 datetest 16.6 {datetime(0,'+464269060799 seconds')} {9999-12-31 23:59:59} 504 datetest 16.7 {datetime(0,'+464269060800 seconds')} NULL 515 datetest 16.20 {datetime(5373484.4999999,'-464269060799 seconds')} \ 517 datetest 16.21 {datetime(5373484,'-464269060800 seconds')} NULL [all …]
|
| H A D | walblock.test | 77 # 4. Still in xShmBarrier(), wait for 5 seconds. Check that the other 80 # 5: Finish committing the transaction. Then wait for 0.5 seconds more. 96 do_test "1.2.2.(blocking 10 seconds)" { 106 do_test "1.2.3.(blocking 0.5 seconds)" {
|
| H A D | thread003.test | 78 puts "Starting thread003.2 (should run for ~$nSecond seconds)" 114 puts "Starting thread003.3 (should run for ~$nSecond seconds)" 153 puts "Starting thread003.4 (should run for ~$nSecond seconds)"
|
| H A D | selectG.test | 21 # that this insert happens quickly (in less than 10 seconds). Actually, the 22 # insert will normally happen in less than 0.5 seconds on a workstation, but
|
| H A D | notify2.test | 33 # Each thread repeats transactions over and over for 20 seconds. Each 101 # This loop runs for ~20 seconds. 203 puts "Running $xStep test for $nSecond seconds"
|
| H A D | date3.test | 44 # timestamp - the number of seconds since 1970-01-01 00:00:00 UTC. 115 # Unix Time - the number of seconds since 1970.
|
| H A D | date2.test | 113 ('+10 seconds'), 114 ('-10 seconds'),
|
| H A D | sort4.test | 43 # Minimum number of seconds to run for. If the value is 0, each test 205 do_test "$testprefix-([expr $iTimeLimit-$iNow] seconds remain)" {} {}
|
| H A D | thread005.test | 98 # The test runs for 20 seconds or until one of the "SELECT count(*)" 218 puts "Running thread-tests for ~20 seconds"
|
| H A D | sort2.test | 69 # Because it uses so much data, this test can take 12-13 seconds even on
|
| H A D | trace3.test | 132 list $stmt [expr {$ns >= 0 && $ns <= 9999999}]; # less than 0.010 seconds 142 list $stmt [expr {$ns >= 0 && $ns <= 9999999}]; # less than 0.010 seconds
|
| H A D | soak.test | 48 # seconds.
|
| H A D | fuzzer2.test | 40 puts "This test is slow - perhaps around 7 seconds on an average pc"
|
| H A D | fts4merge3.test | 40 set msg "this takes around 12 seconds"
|
| H A D | table.test | 639 unset -nocomplain date time seconds 640 foreach {date time seconds} { 647 set sqlite_current_time $seconds
|
| H A D | walprotocol.test | 83 puts "# Normally this equates to a delay of roughly 10 seconds, but if SQLite"
|
| H A D | swarmvtab.test | 88 do_execsql_test 1.5.1.(5-seconds-or-so) {
|
| H A D | fts3an.test | 191 puts "This next test can take a little while (~ 30 seconds)..."
|
| /sqlite-3.40.0/tool/ |
| H A D | mksqlite3internalh.tcl | 44 set today [clock format [clock seconds] -format "%Y-%m-%d %H:%M:%S UTC" -gmt 1]
|
| H A D | mksqlite3c-noext.tcl | 61 set today [clock format [clock seconds] -format "%Y-%m-%d %H:%M:%S UTC" -gmt 1]
|
| H A D | mksqlite3c.tcl | 84 set today [clock format [clock seconds] -format "%Y-%m-%d %H:%M:%S UTC" -gmt 1]
|
| /sqlite-3.40.0/ext/fts2/ |
| H A D | mkfts2amal.tcl | 25 set today [clock format [clock seconds] -format "%Y-%m-%d %H:%M:%S UTC" -gmt 1]
|
| /sqlite-3.40.0/ext/fts5/test/ |
| H A D | fts5bigpl.test | 51 # 5-byte varint. This test takes 30 seconds or so on a 2014 workstation.
|
12