https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98823
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I don't have access to the box where it happened, I was just lucky somebody else had and could find the stuck process for me and kill it. In the past 2 month gcc builds were stuck similar way several times but I didn't have anybody to tell me what is going on and therefore I just killed the builds and retried, so no idea if it was go or something else. Anyway, guess we could try to do a go test that will just sleep for 20 minutes and see if it gets killed with timeout, and similarly a go test that will do say a busy loop and see if it gets killed.
