This is also reproducible on rhel-8.6 with delve-1.7.2-1.module+el8.6.0+12972+ebab5911 and latest golang-1.17.12-6.el8_6.0.0.1 build.

+++ This bug was initially created as a clone of Bug #2091666 +++

Description of problem:
TestNextParked from devtools-2022.2 go-toolset-1.17-delve-1.7.2-1.el7_9 internal testsuite fails on RHEL-7.9-updates-20220512.1.

Version-Release number of selected component (if applicable):
go-toolset-1.17-delve-1.7.2-1.el7_9
go-toolset-1.17-golang-1.17.10-1.el7_9
go-toolset-1.17-1.17.10-1.el7_9

How reproducible:
Usually reproducible on 1minutetip machines; also seen on kvm-01-guest14.lab.eng.brq.redhat.com.

Steps to Reproduce:
1. scl enable go-toolset-1.17 bash
2. rpm -ivh go-toolset-1.17-delve-1.7.2-1.el7_9.src.rpm
3. rpmbuild -bp rpmbuild/SPECS/delve.spec
4. cd rpmbuild/BUILD/delve-1.7.2/_build/
5. export GO111MODULE=off
6. export GOPATH=$(pwd)
7. go test github.com/go-delve/delve/service/dap -v -count 1

Actual results:
(...)
=== RUN TestNextParked
DAP server listening at: [::]:34248
Connecting to server at: [::]:34248
hi 9
hi 9
hi 0
hi 0
hi 1
hi 1
hi 2
hi 2
hi 3
hi 3
hi 4
hi 4
hi 5
hi 5
hi 6
hi 6
hi 7
hi 7
hi 8
hi 8
server_test.go:3635: got &dap.TerminatedEvent{Event:dap.Event{ProtocolMessage:dap.ProtocolMessage

, Event:"terminated"}, Body:dap.Termi
natedEventBody{Restart:interface {}(nil)}}, want *dap.StoppedEvent
— FAIL: TestNextParked (0.46s)
(...)