Skip to content

Conversation

@MDrakos
Copy link
Member

@MDrakos MDrakos commented Nov 20, 2025

No description provided.

Copy link
Collaborator

@mitchell-as mitchell-as left a comment

Choose a reason for hiding this comment

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

This looks good, but we don't need to skip ARM tests. See my comment below.

Comment on lines +118 to +123
// SkipUnsupportedArchitectures will skip tests for unsupported system architectures
func (suite *Suite) SkipUnsupportedArchitectures() {
if runtime.GOOS == "linux" && runtime.GOARCH == "arm64" {
suite.T().Skip("Skipping test on Linux/arm64 - platform not configured")
}
}
Copy link
Collaborator

@mitchell-as mitchell-as Nov 25, 2025

Choose a reason for hiding this comment

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

We don't need this and the subsequent calls to this function in follow up tests because we'll have to add this to every integration test we tag until we have arm64 support for the projects we use.

The arm runner is for ensuring State Tool can be installed and used on ARM systems -- we have tests that do pass on ARM as part of the nightly suite.

For the time being we accept that our ARM tests will fail when we explicitly tag tests for running on CI until we get around to adding ARM support to our ActiveState-CLI test projects.

The nightly arm runner should not have any failing tests though. For example, see last night's success: https://github.com/ActiveState/cli/actions/runs/19653720289/job/56285920214

Copy link
Member Author

Choose a reason for hiding this comment

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

Are the tests that pass on ARM all unit tests? The link you provided is skipping all integration tests on ARM.

I'm okay to remove this but would prefer to not have failing tests on PRs if there's an easy way to avoid it. Can we skip integration tests on PRs for arm as well or is that currently useful?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants