`metric_calculator_test` is failing on ARM

[atoulme]

Description

=== FAIL: . TestSweep (0.00s)
make[1]: *** Waiting for unfinished jobs....
    metric_calculator_test.go:276: 
        	Error Trace:	/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/internal/aws/metrics/metric_calculator_test.go:276
        	Error:      	"1.892346ms" is not less than or equal to "1ms"
        	Test:       	TestSweep

=== FAIL: . TestSweep (re-run 1) (0.00s)
    metric_calculator_test.go:276: 
        	Error Trace:	/home/runner/work/opentelemetry-collector-contrib/opentelemetry-collector-contrib/internal/aws/metrics/metric_calculator_test.go:276
        	Error:      	"1.9[58](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/13532271051/job/37816975925?pr=38204#step:7:59)426ms" is not less than or equal to "1ms"
        	Test:       	TestSweep

https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/13532271051/job/37816975925?pr=38204

[github-actions]

Pinging code owners for internal/aws: @Aneurysm9 @mxiamxia. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[dehaansa]

From what I am reading, line 276 here doesn't appear to be an effective test, due to the behavior of the time.NewTicker used in mwe.Sweep.

According to the go source the time returned on the ticker.C channel is always the expected time from the ticker, even if it was not able to schedule to send at that time. This means that line 276 isn't really testing the behavior of the code, just the behavior of the scheduler.

for i := 1; i <= 2; i++ {
	// sweepTime is the time that the internal ticker _expected_ to tick, may not be close (1ms) to the current time
	sweepTime := <-sweepEvent
	// tickTime is the time since test start plus the # of expected ticks
	tickTime := time.Since(start) + mwe.ttl*time.Duration(i)
	require.False(t, closed.Load())
	// This is asserting that the ttl is less than or equal to the time since the start captured before the mwe.sweep function was called,
	// so it's asserting that time consumed until now is greater than one ttl. Should probably be ttl * i, and tickTime should just be time.Since(start)
	assert.LessOrEqual(t, mwe.ttl, tickTime)
	// This is asserting that the time since the _expected_ current tick time is less than or equal to the ttl.
	// This is just testing if the internal timer got to schedule its tick well, and isn't late? This is go runtime behavior, not MWE behavior.
	assert.LessOrEqual(t, time.Since(sweepTime), mwe.ttl)
}

[atoulme]

What should we do @dehaansa ?

[dehaansa]

What should we do @dehaansa ?

I was hoping for some codeowner input, as my read of this could be incorrect. I would be in favor of just removing the last assert in this test, and a small modification to the second to last assert. I'll make a proposed fix PR.

[dehaansa]

Proposed change, waiting for tests to validate. #38431