Round 2: Adapt to randomly generated nop component names in unit tests #31659
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.
Description:
Follow-up to #31640
I didn't realize the contrib test stopped after the first failure, so there were a few more failures for open-telemetry/opentelemetry-collector#9637.
I verified that this passes the contrib-tests check for the core repo locally, so this should be the rest of them.
For the splunkhec exporter, the exporter actually uses
ID.String()
:opentelemetry-collector-contrib/exporter/splunkhecexporter/client.go
Line 71 in 4c5b5e9
The filelog receiver was assuming that
NewNopCreateSettings
returned the same ID, so I re-used the create settings in the test.Link to tracking Issue:
Blocking open-telemetry/opentelemetry-collector#9637
@dmitryax @Aneurysm9 @codeboten