tests: query interrupt was both slow and possibly incorrect - added a timeout and use pytest.raises with a more interruptable query

Author: paultiq

tests/fast/api/test_query_interrupt.py

@@ -1,35 +1,31 @@
 import duckdb
 import time
 import pytest
-
 import platform
 import threading
 import _thread as thread
 
 
 def send_keyboard_interrupt():
-    # Wait a little, so we're sure the 'execute' has started
     time.sleep(0.1)
-    # Send an interrupt to the main thread
     thread.interrupt_main()
 
 
 class TestQueryInterruption(object):
+    
     @pytest.mark.xfail(
         condition=platform.system() == "Emscripten",
         reason="Emscripten builds cannot use threads",
     )
-    def test_query_interruption(self):
+    @pytest.mark.timeout(15)
+    def test_keyboard_interruption(self):
         con = duckdb.connect()
         thread = threading.Thread(target=send_keyboard_interrupt)
         # Start the thread
         thread.start()
         try:
-            res = con.execute('select count(*) from range(100000000000)').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
-            assert True
-        except KeyboardInterrupt:
-            pytest.fail()
-        thread.join()
+            with pytest.raises((KeyboardInterrupt, RuntimeError)):
+                res = con.execute('select * from range(100000) t1,range(100000) t2').fetchall()
+        finally:
+            # Ensure the thread completes regardless of what happens
+            thread.join()