[internal/aws] Flaky test TestSweep on Windows

[pjanotti]

Component(s)

internal/aws

Describe the issue you're reporting

Test failure on unrelated change https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/6588556890/job/17901091034?pr=27864#step:6:503

make[2]: Entering directory 'D:/a/opentelemetry-collector-contrib/opentelemetry-collector-contrib/internal/aws/metrics'
go test -race -timeout 300s -parallel 4 --tags="" ./...
--- FAIL: TestSweep (0.24s)
    metric_calculator_test.go:276: 
        	Error Trace:	D:/a/opentelemetry-collector-contrib/opentelemetry-collector-contrib/internal/aws/metrics/metric_calculator_test.go:276
        	Error:      	"2.2815ms" is not less than or equal to "1ms"
        	Test:       	TestSweep
FAIL
FAIL	github.com/open-telemetry/opentelemetry-collector-contrib/internal/aws/metrics	0.591s
FAIL

[github-actions]

Pinging code owners:

• internal/aws: @Aneurysm9 @mxiamxia

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

[bryan-aguilar]

This is a side effect of the test requiring an action to be done within a certain time frame which can be dependent on many factors. We could take a look at the test case again to see if bigger headroom is a suitable solution or if we should remove the timing assertion all together.

[pjanotti]

A few more recent hits:

• https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/6985213001/job/19009183114#step:6:516
• https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/7013875651/job/19080701612#step:6:516

[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.

Pinging code owners:

• internal/aws: @Aneurysm9 @mxiamxia

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

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.