Closed albertteoh closed 11 months ago
I thought we already have open ticket for this test
I thought we already have open ticket for this test
I could only find this closed one: https://github.com/jaegertracing/jaeger/issues/4743.
Documenting another flaky test failure data point in the main
branch: https://github.com/jaegertracing/jaeger/actions/runs/6435789834/job/17477774812#step:7:4569
I don't think that one should've been closed, I'll reopen. Let's keep discussion on the original ticket as it has more context already.
Closing this as duplicate of #4743
Duplicate of #4743
What happened?
A CI run from https://github.com/jaegertracing/jaeger/pull/4802 had a failing unit test job with error:
Steps to reproduce
Hard to reproduce, even with:
Expected behavior
Test should pass.
Relevant log output
Screenshot
No response
Additional context
From the two log lines, we see two different passwords provided in the Authorization header:
From the log output, it looks like the old client hasn't been properly closed and so is making requests alongside the new client, and so there's a race condition on the last write to
authReceived
. In the failing test case, it looks like the old client makes the last write.Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response