tests: add a longer sleep to the query interrupt tests, due to free threading starting it earlier

Author: paultiq

tests/fast/api/test_connection_interrupt.py

@@ -16,13 +16,14 @@ def test_connection_interrupt(self):
 
         def interrupt():
             # Wait for query to start running before interrupting
-            time.sleep(0.1)
+            time.sleep(1)
             conn.interrupt()
 
         thread = threading.Thread(target=interrupt)
         thread.start()
         with pytest.raises(duckdb.InterruptException):
-            conn.execute("select count(*) from range(100000000000)").fetchall()
+            conn.execute('select * from range(100000) t1,range(100000) t2').fetchall()
+
         thread.join()
 
     def test_interrupt_closed_connection(self):

tests/fast/api/test_query_interrupt.py

@@ -9,7 +9,7 @@
 
 def send_keyboard_interrupt():
     # Wait a little, so we're sure the 'execute' has started
-    time.sleep(0.1)
+    time.sleep(1)
     # Send an interrupt to the main thread
     thread.interrupt_main()
 
@@ -25,7 +25,7 @@ def test_query_interruption(self):
         # Start the thread
         thread.start()
         try:
-            res = con.execute('select count(*) from range(100000000000)').fetchall()
+            con.execute('select * from range(100000) t1,range(100000) t2').fetchall()
         except RuntimeError:
             # If this is not reached, we could not cancel the query before it completed
             # indicating that the query interruption functionality is broken