Skip to content
New issue

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

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

Already on GitHub? # to your account

ci: Enable ccruntime-e2e and makefile test on arm64 #484

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

seungukshin
Copy link

This changes enables e2e and makefile test on arm64 runner. There are some prerequisite.

Ther operator's CI is as following: (${\color{red}red}$ parts are added by this change)

  • ccruntime-nightly (executed at 02:00 everyday)
    • call ccruntime-e2e (e2e test on amd64, s390x, ${\color{red}arm64}$)
  • ccruntime-pr (exectued at pull request)
    • call ccruntime-e2e (e2e test on amd64, s390x, ${\color{red}arm64}$)
  • docker-publish-latest-on-merge (build images on amd64)
  • docker-publish-on-tag (build images on amd64)
  • enclave-cc-cicd (sgx specific test on amd64)
  • enclave-cc-e2e (sgx specific test on amd64)
  • gofmt (lint on amd64)
  • golangci-lint (lint on amd64)
  • makefile
    • build test on amd64, ${\color{red}arm64}$
    • lib-codeql (static analysis on amd64)
    • envtest on amd64, ${\color{red}arm64}$

@seungukshin
Copy link
Author

e2e test on ubuntu-20.04 failed because of DiskPressure which required 15% of free space (14% on ubunut-20.04). So I added a commit to move GOPATH to /mnt fo free more space on / (now 16% on ubuntu-20.04). I confirmed e2e test passed on ubunut-20.04 after this change. (https://github.com/seungukshin/operator/actions/runs/12866737850/job/35871382480)

@seungukshin
Copy link
Author

@seungukshin
Copy link
Author

Some part of change is merged as a part of this PR, so resolved the merge conflict.

Test results on ubuntu-22.04, ubuntu-20.04 and ubuntu-22.04-arm: https://github.com/seungukshin/operator/actions/runs/12932473305

@seungukshin seungukshin force-pushed the arm64-ci branch 2 times, most recently from a1ec013 to 48d7575 Compare January 29, 2025 13:24
@seungukshin
Copy link
Author

I'll close and reopen this PR because the build test stuck "Expected — Waiting for status to be reported" status while all the others passed already. It seems there is no concrete solution for this yet. - https://github.com/orgs/community/discussions/26698#discussioncomment-10769359
image

@seungukshin seungukshin closed this Feb 7, 2025
@seungukshin seungukshin reopened this Feb 7, 2025
Copy link
Contributor

@ldoktor ldoktor left a comment

Choose a reason for hiding this comment

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

lgtm, looking forward to seeing arm runner covvered :-)

Signed-off-by: Seunguk Shin <seunguk.shin@arm.com>
Reviewed-by: Nick Connolly <nick.connolly@arm.com>
Reviewed-by: Tao Xu <tao.xu@arm.com>
@seungukshin
Copy link
Author

Thank you for your review, @ldoktor !
@stevenhorsman , @zvonkok and @fidencio , could you take a look on this? Two CI test cases failed but they are because of rate limit from docker.io. (build is still not executed though)

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants