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

ci: Enable ci tests on arm64 #890

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

seungukshin
Copy link

This changes enables CI tests on arm64 runner.

Ther guest-components's CI is as following: (${\color{red}red}$ parts are added by this change, links are test results on forked repo.)

@seungukshin seungukshin requested a review from a team as a code owner January 28, 2025 13:40
Signed-off-by: Seunguk Shin <seunguk.shin@arm.com>
Reviewed-by: Nick Connolly <nick.connolly@arm.com>
@seungukshin
Copy link
Author

rust on aarch64-unknown-linux-gnu has a bug which faces SIGSEGV intermittently (rust-lang/rust#135867) with 1.83.0 or later. I added a commit to use rust 1.82.0 instead.

PR test results in the forked repo.: seungukshin#4

@seungukshin
Copy link
Author

Retest with new rust stable (1.84.0 -> 1.84.1) passed, so I removed the commit to force 1.82.0.

PR test results in the forked repo.: seungukshin#5

@seungukshin
Copy link
Author

Possibility is reduced, but getting SIGSEGV happened from time to time.

Added a commit to make arm64 uses 1.82.0 only and the rest of architecture use the same (stable and 1.83.0)

PR test results in the forked repo.: seungukshin#5

@seungukshin seungukshin force-pushed the arm64-ci branch 2 times, most recently from fec8f3c to fd54a8f Compare February 5, 2025 09:48
rust on aarch64-unknown-linux-gnu has a bug which faces SIGSEGV
intermittently (rust-lang/rust#135867)
with 1.83.0 or later.
rust 1.82.0 will be used for arm64 only until the above issue is resolved.

Signed-off-by: Seunguk Shin <seunguk.shin@arm.com>
@seungukshin
Copy link
Author

It seems one random test case kept failing at Code Checkout step every retry.

It does not contain any error message and it couldn't be reproduced in the forked repo. Could anyone help me to retry with debug enabled?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant