[receiver/prometheus] Unit test failure: TestScopeInfoScopeAttributes

[crobert-1]

Component(s)

receiver/prometheus

Describe the issue you're reporting

CI failure link

Test failure output:

    --- FAIL: TestScopeInfoScopeAttributes/target1 (0.00s)
        metrics_receiver_labels_test.go:771: 
            	Error Trace:	/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/receiver/prometheusreceiver/metrics_receiver_labels_test.go:771
            	            				/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/receiver/prometheusreceiver/metrics_receiver_helper_test.go:652
            	Error:      	Not equal: 
            	            	expected: "scope.with.attributes"
            	            	actual  : "fake.scope.name"
            	            	
            	            	Diff:
            	            	--- Expected
            	            	+++ Actual
            	            	@@ -1 +1 @@
            	            	-scope.with.attributes
            	            	+fake.scope.name
            	Test:       	TestScopeInfoScopeAttributes/target1
FAIL
	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver	coverage: 54.5% of statements
FAIL	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver	242.654s
ok  	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver/internal	7.224s	coverage: 90.5% of statements
FAIL
make[2]: *** [../../Makefile.Common:105: test-with-cover] Error 1

This is a new test, added in PR #25898. It appears as if the test data may not preserve the ordering it's defined in, so we check for what we expect to be the first scope name, but it's actually the second defined value. It seems to be parsing data properly. I think the test just needs to be updated to properly account for un-ordered data, or sort the data somehow before checking values.

[github-actions]

Pinging code owners:

• receiver/prometheus: @Aneurysm9 @dashpole

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[dashpole]

I'll get this fixed. Thanks