This mostly happens in CI, but I've observed sometimes the cljstyle check task hangs with no output for 10+ minutes and gets killed for inactivity. Occasionally we do see some output warning that not all of the threads have completed in the expected time interval.
Investigate, and potentially add some internal state dumping if we go way beyond the expected runtime.
I made the timeout configurable in f5adb14ae610ffd3cdfae4aeb49c74e61e4adb61 and added thread stack dumping in 324314f388799327a5321b166a5ebcc691882a2e, which should help diagnose this.
This mostly happens in CI, but I've observed sometimes the
cljstyle check
task hangs with no output for 10+ minutes and gets killed for inactivity. Occasionally we do see some output warning that not all of the threads have completed in the expected time interval.Investigate, and potentially add some internal state dumping if we go way beyond the expected runtime.