Closed derekparker closed 10 months ago
if it's podman that's crashing it should be reported to them it's not clear that this is an issue with go itself
if it's podman that's crashing it should be reported to them it's not clear that this is an issue with go itself
I'm happy to open an issue there as well, however this is a fatal error from the Go runtime, not user code.
Timed out in state WaitingForInfo. Closing.
(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Has not been tested.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run
tmt run -arv provision -h container plan -n /remote
See https://github.com/teemtee/tmt/issues/1735 for more information.
What did you expect to see?
No fatal error.
What did you see instead?
fatal: systemstack called from unexpected goroutine