[
https://issues.apache.org/jira/browse/YUNIKORN-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814114#comment-17814114
]
Craig Condit commented on YUNIKORN-2378:
----------------------------------------
I really don’t think this is worth pursuing. We don’t compile with cgo, so the
only architecture-specific code we have is contained within the go standard
library itself. The one issue in the last two years that I’m aware of that was
architecture-specific was a broken test that made assumptions about undefined
behavior with rounding of extremely large floating point values.
Running our CI already kicks off 12 different e2e builds and doubling this to
support a platform that is maybe 1% of our user base isn’t a good use of
resources.
> 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]
