-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[extension/jaegerremotesampling] Flaky test - TestStartAndShutdownRemote #9113
Comments
Fixes #9113 Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Fixes #9113 Signed-off-by: Juraci Paixão Kröhling <[email protected]>
This failed again here: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/7957402089?check_suite_focus=true#step:8:940
|
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
Since the port is already allocated in line opentelemetry-collector-contrib/extension/jaegerremotesampling/extension_test.go Lines 57 to 58 in ea97fda
I changed === 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. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
We just hit this again:
|
Just hit this again:
|
I have experienced the same in https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/4387063396/jobs/7685532139#step:9:520 |
Logs:
The text was updated successfully, but these errors were encountered: