canonical / canonical/observability
run itests using ARM runners
- Dominant language
- Just
- Stars
- 10
- Forks
- 25
- Avg merge
- 6h 3m
- Merged PRs (30d)
- 7
Description
Similar to the case of [`charm-release`](https://github.com/canonical/observability/blob/main/.github/workflows/charm-release.yaml#L161), I believe we'd want our integration tests to also run on `amd64` and `arm64` runners if the charm needs to. This would be particular useful for our machine charms that release to arm (i.e. the collector and the profiler)
Contributor guide
Research direction
Start with .github/workflows/charm-release.yaml around the referenced runner configuration, then locate the workflow or job that runs integration tests. Compare how amd64 and arm64 runners are selected and verify the affected machine charms run their integration tests on both architectures. Done means the relevant integration-test workflow covers both runners without breaking existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100