Closed moroten closed 2 years ago
Hmmm.... Interesting. It looks like this is the cause for it: https://github.com/golang/go/issues/19326
There's no guarantee the signal gets delivered to the same OS thread, it seems. Let's merge this then.
Oh, wait. Could you maybe add a // comment
here along these lines?
This code should not be reached, if it weren't for the fact that process.Signal() does not guarantee that the signal is delivered to the same thread.
Added a comment with a link to the golang ticket.
remote-apis-testing shows the following log in https://gitlab.com/remote-apis-testing/remote-apis-testing/-/jobs/2773967861
Apparently, the panic line was reached before the signal had been handled and the process killed, so just remove it.