Shut down executor threads after timeout to prevent JaCoCo EOFException

mrigger · claude · mrigger · commit 9385f39dd3df · 2026-03-26T23:42:32.000+08:00
When executeMain times out, awaitTermination returns but worker threads
remain running (non-daemon). For remote DBs like Materialize, threads
blocked on network I/O prevent the JVM from exiting cleanly, causing
surefire to forcibly kill the process before JaCoCo can flush jacoco.exec,
resulting in an EOFException during report generation.

Calling shutdownNow() after the timeout interrupts threads (PostgreSQL
JDBC socket reads respond to Thread.interrupt()), allowing them to exit
and JaCoCo to write complete coverage data.

Co-Authored-By: Claude Sonnet 4.6 &lt;noreply@anthropic.com&gt;
diff --git a/src/sqlancer/Main.java b/src/sqlancer/Main.java
@@ -715,6 +715,7 @@ private boolean run(MainOptions options, ExecutorService execService,
                 execService.awaitTermination(Long.MAX_VALUE, TimeUnit.DAYS);
             } else {
                 execService.awaitTermination(options.getTimeoutSeconds(), TimeUnit.SECONDS);
+                execService.shutdownNow();
             }
         } catch (InterruptedException e) {
             e.printStackTrace();

Original file line number	Diff line number	Diff line change
`@@ -715,6 +715,7 @@ private boolean run(MainOptions options, ExecutorService execService,`
`715`	`715`	`execService.awaitTermination(Long.MAX_VALUE, TimeUnit.DAYS);`
`716`	`716`	`} else {`
`717`	`717`	`execService.awaitTermination(options.getTimeoutSeconds(), TimeUnit.SECONDS);`
	`718`	`+ execService.shutdownNow();`
`718`	`719`	`}`
`719`	`720`	`} catch (InterruptedException e) {`
`720`	`721`	`e.printStackTrace();`