internal/telemetry: fix flake in TestTelemetryEnabled #3160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Locks the
mockClient
before updating the values inMetrics
. Also adds an improved error message for the previously failing line.Closes APMLP-319
Motivation
There was a flake in which
TestTelemetryEnabled/tracer_start
did not find the correct init time due to a data race, causing random failures that impacts the health of the tracer. In the off chance that the flake reappears, the new error message should help with debugging more thoroughly.Running the test ~
2000
times on both a MacOS computer and in a Windows VM passed. Rerunning CI a few times also only gave successes.Reviewer's Checklist
v2-dev
branch and reviewed by @DataDog/apm-go.Unsure? Have a question? Request a review!