[ 
https://issues.apache.org/jira/browse/YUNIKORN-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814108#comment-17814108
 ] 

Dong-Lin Hsieh commented on YUNIKORN-2378:
------------------------------------------

cc [~ccondit]  [~chia7712] 

I believe it's essential to test our artifact on ARM architecture, as our 
current CI setup only operates on x86.

[How can I specify the architecture in GitHub 
Actions?|https://stackoverflow.com/questions/71217505/how-can-i-specify-the-architecture-in-github-actions]

Furthermore, GitHub has indicated that support for running GitHub Actions on 
ARM architecture is forthcoming, currently in a private beta phase, as detailed 
in their roadmap: [GitHub Roadmap Issue 
#836|https://github.com/github/roadmap/issues/836].

We have two options:
 # Temporarily use the M1 architecture to test our ARM compatibility, and 
switch back to Linux/ARM when GitHub Actions support becomes publicly available.
 # Revisit this matter once Linux/ARM support for GitHub Actions is publicly 
available.

> Run GitHub Actions on  M1 Mac Machine
> -------------------------------------
>
>                 Key: YUNIKORN-2378
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2378
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - common, shim - kubernetes, webapp, website
>            Reporter: Dong-Lin Hsieh
>            Assignee: Dong-Lin Hsieh
>            Priority: Major
>
> [GitHub Actions Introducing the new M1 macOS runner available to open 
> source|https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/]
> Node.js officially uses M1 in their GitHub Actions.
> [https://github.com/nodejs/node/pull/51620]
> It is beneficial to also test our CI on Mac ARM machines.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to