Closed jpkrohling closed 1 year ago
This failed again here: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/7957402089?check_suite_focus=true#step:8:940
=== RUN TestStartAndShutdownRemote
extension_test.go:83:
Error Trace: /home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/extension/jaegerremotesampling/extension_test.go:83
Error: Received unexpected error:
error while starting the gRPC server: failed to listen on gRPC port: listen tcp :14250: bind: address already in use
Test: TestStartAndShutdownRemote
cc @frzifus, I think I pinged you on the wrong issue. I wanted to ping you on this one here. Sorry about the noise.
Sure, i can take over :)
i wonder that it fails in line 83
.
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/ea97fda88d979b29b31885bd8dc9f116ef983d5e/extension/jaegerremotesampling/extension_test.go#L83
Since the port is already allocated in line 58
.
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/ea97fda88d979b29b31885bd8dc9f116ef983d5e/extension/jaegerremotesampling/extension_test.go#L57-L58
I changed localhost:0
to localhost:8080
while blocking that port with nc -l -p 8080
.
Then i see:
=== RUN TestStartAndShutdownRemote
extension_test.go:58:
Error Trace: /home/frzifus/git/go/observability/opentelemetry-collector-contrib/extension/jaegerremotesampling/extension_test.go:58
Error: Received unexpected error:
listen tcp 127.0.0.1:8080: bind: address already in use
Test: TestStartAndShutdownRemote
--- FAIL: TestStartAndShutdownRemote (0.00s)
FAIL
exit status 1
If you take a closer look at the extention start method, only a connection to the server is established but no port is allocated.
What do you think about adding a retry mechanism to the test evaluation?
Pinging code owners: @jpkrohling. See Adding Labels via Comments if you do not have permissions to add labels yourself.
What do you think about adding a retry mechanism to the test evaluation?
That might be worth trying, but this failure pattern happens elsewhere. I think there's an underlying problem we need to solve, I just don't know yet which problem this is. Without digging too much into it, I would guess this is related to how we run the tests (with -race and some parallel test executions).
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
We just hit this again: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/3851828150/jobs/6563425908
=== RUN TestStartAndShutdownRemote
extension_test.go:83:
Error Trace: /home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/extension/jaegerremotesampling/extension_test.go:83
Error: Received unexpected error:
error while starting the gRPC server: failed to listen on gRPC port: listen tcp 127.0.0.1:14250: bind: address already in use
Test: TestStartAndShutdownRemote
--- FAIL: TestStartAndShutdownRemote (0.00s)
Just hit this again:
=== RUN TestStartAndShutdownRemote
extension_test.go:83:
Error Trace: /home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/extension/jaegerremotesampling/extension_test.go:83
Error: Received unexpected error:
error while starting the gRPC server: failed to listen on gRPC port: listen tcp 127.0.0.1:14250: bind: address already in use
Test: TestStartAndShutdownRemote
I have experienced the same in https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/4387063396/jobs/7685532139#step:9:520
Logs: