Flaky test - prometheusreceiver - TestOpenMetricsNegative

[jpkrohling]

Seen here: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/5869686660?check_suite_focus=true#logs

2022-04-07T14:06:18.1333771Z === RUN   TestOpenMetricsNegative/bad_type_1
2022-04-07T14:06:18.1334163Z race: limit on 8128 simultaneously alive goroutines is exceeded, dying
2022-04-07T14:06:18.1334861Z FAIL	github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver	102.534s

cc @Aneurysm9 @dashpole

[jpkrohling]

And here: https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/5860025725?check_suite_focus=true

[gouthamve]

Looks like it will be fixed in the next release of Go: golang/go#47056 (comment)

[dmitryax]

https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/5980689286

[tigrannajaryan]

Failed again https://github.com/open-telemetry/opentelemetry-collector-contrib/runs/5993262462?check_suite_focus=true

[tigrannajaryan]

4 failures in 4 days. I think we need to disable the test until it is fixed.

[github-actions]

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

Pinging code owners: @Aneurysm9 @dashpole. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jpkrohling]

It looks like this might have been fixed, but a positive confirmation from the code owner(s) is desirable.

[dashpole]

This has been reenabled for a few months without complaint