I’m occassionally seeing my build stuck at ‘termination’ looking like this:

BUILD SUCCESSFUL in 23m 57s
1395 actionable tasks: 1178 executed, 217 up-to-date
<-------------> 0% WAITING
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE
> IDLE

Is this a known issue? Is it worth a Github issue? Reproduction isn’t reliable, and it’s happening in a large proprietary code base.

IMO, Looks like a deadlock / livelock type of situation perhaps? I'd turn off any parallelization you've got enabled and see if that helps / look for any odd task inputs / outputs. Especially accidentally undeclared inputs / outputs. Alternatively, if your proprietary code is recording build metrics somewhere and that process fails or hangs you can get stuck in this kind of state too (I've done this one to myself!)

I’ve got thread dumps from all the gradle processes if any enterprising Gradle engineer wants to look at them… when I have the time I’ll look again at task inputs/output… but there’s a lot going on in the build… 150 projects, Docker, NodeJS, and a whole ton of Java code. It’s a potential bottomless pit of debugging!

😵 Good luck!! If all else fails and most of the build is cached you could always do something like start it with a reasonable timeout and kill and re-run to get it to "finish" correctly. That's definitely the 🙈 approach though.