[test] Test_PushMetricsConcurrent fails on Windows 2025 GH runner

[pjanotti]

Component(s)

exporter/prometheusremotewrite

Describe the issue you're reporting

Detected via #37025 - the test is failing consistently on the Windows 2025 GH runner. Opening this issue so we can enable tests on Windows 2025 while this test failure is investigated.

Related to #37024

[github-actions]

Pinging code owners:

• exporter/prometheusremotewrite: @Aneurysm9 @rapphil @dashpole @ArthurSens

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

[pjanotti]

The test is also failing outside of Windows 2025, but, per PR #37025 it seems more likely to fail on Windows 2025, see https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/12678000508/job/35334640582#step:8:216

[ArthurSens]

Interesting, thanks for the ping. I'm not really experienced with Windows Arch. Do you have any tips on how to debug the problem without a Windows machine?

[pjanotti]

Hi @ArthurSens - scheduling and timing on Windows is really different than *nix. In this case I suspect that is the blasting of requests in goroutines done in the test that somehow is causing the trouble on Windows. Limiting the number of pending requests may help.

Another hit: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/12807789524/job/35709129938#step:8:8604

[pjanotti]

https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/12832998168/job/35787006365#step:8:40