feat: add support for arm64 - #37
Merged
Merged
Conversation
michaeldmitry
force-pushed
the
TAP-727
branch
from
September 11, 2025 06:57
e9b0c59 to
f2d9511
Compare
Gmerold
reviewed
Sep 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #27
Currently our CI doesn’t run itests using arm runners → fix
But, even when it does, it won’t work for our case. ATM, our self-hosted arm runners + gh arm runners don’t support nested virtualisation. Meaning that, juju won’t be able to deploy a machine of type
virtual-machine, which is what we need for the profiler to work.Sample error logs when trying to run the itests on arm runners
UPDATE
Ran local tests locally on an arm machine and they all passed