Closed aartiPl closed 1 year ago
Seems that, in my case, it was a problem with the process waiting for input from the input stream. It wasn't easy to debug because Gradle hadn't logged the currently running test case correctly. Only after enabling --debug in the Gradle was I able to see what exact test case hanged my process. I am not sure if it is possible to do anything about that in Github actions, so I am closing the ticket.
Here is the log from the hanging process in kscript (https://github.com/kscripting/kscript/)
https://pipelines.actions.githubusercontent.com/serviceHosts/47bf7b7d-0c3a-455a-acb6-c89dfcc08bb1/_apis/pipelines/1/runs/273/signedlogcontent/2?urlExpires=2022-11-16T15%3A22%3A09.3235876Z&urlSigningMethod=HMACV1&urlSignature=iufPCBsUF5aLCE5j%2FM%2F%2Bzs5H0AFu1hvWfJSMggTJbLo%3D
I have added many debugging commands in the code (including a list of all java/bash processes), but I still have no clue why it hangs. The tests seem to hang between the execution of JUnit test classes. Unfortunately, the raw logs do not help resolve the issue.
Is there any way to debug such cases? Unfortunately, I can not reproduce it locally, so it is tough to resolve the issue.
See also: https://github.com/actions/runner/issues/1326