Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore] enable running ARM builds by default #38204

Merged
merged 5 commits into from
Mar 7, 2025

Conversation

atoulme
Copy link
Contributor

@atoulme atoulme commented Feb 25, 2025

Description

Run ARM builds on any PR.

Link to tracking issue

Fixes #38198

@atoulme atoulme requested a review from a team as a code owner February 25, 2025 22:32
@atoulme atoulme requested a review from dehaansa February 25, 2025 22:32
@dehaansa
Copy link
Contributor

Hostmetrics tests should be fixed in #38211

@songy23 songy23 added the ci-cd CI, CD, testing, build issues label Feb 26, 2025
Copy link
Member

@songy23 songy23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need rebase / merge main

@dehaansa
Copy link
Contributor

dehaansa commented Mar 4, 2025

Connecting the issue for the failing test because it's not linked and I keep losing track of it: #38205

atoulme pushed a commit that referenced this pull request Mar 6, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
Update the metric_calculator_test's TestSweep to not test the behavior
of the internal go timer in a way that causes arm tests to fail.

On linked issue, I added these comments to the existing test to describe
the existing behavior, this PR drops the last assert and causes the
existing assert to check that the passed clock time is greater than the
expected amount of TTLs, which appears to be the original intent.
```
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)
}
```

<!-- Issue number (e.g. #1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes
#38205
Relevant to
#38204
@atoulme atoulme merged commit 31d8a73 into open-telemetry:main Mar 7, 2025
171 checks passed
@github-actions github-actions bot added this to the next release milestone Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-cd CI, CD, testing, build issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[linux/arm64] Run arm64 build on every PR
5 participants