Open medyagh opened 2 weeks ago
https://github.com/kubernetes/minikube/actions/runs/8472699544/job/23358462960?pr=18531 link to the incorrect github action run
https://github.com/kubernetes/minikube/actions/runs/8472699544/job/23358462960?pr=18531 link to the incorrect github action run
macos-14 (is latest now) in GitHub Actions is only available for arm64.
See here https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source, I fear that I have to rewrite my intel pipelines once macos-12/13 images are removed for GitHub Actions
The macos-14 intel image is exclusively used by azure devops pipelines hosted agents
Describe the bug
We try to run functional test for minikube (using virtualbox) as seen here, how ever it randomly gives us either Arm64 or Intel CPU architecture and there is NO WAY for us to force it to give us only Intel https://github.com/kubernetes/minikube/blob/5eecf3084f2487ceb3cebad33ddfe0006908c941/.github/workflows/pr.yml#L521 we use
To Reproduce
for the full yaml checkout https://github.com/kubernetes/minikube/blob/5eecf3084f2487ceb3cebad33ddfe0006908c941/.github/workflows/pr.yml#L521
Expected behavior
I expect it to give me the CPU architecture not randomly but through a tag such as Arch: x86
Runner Version and Platform
I am using whatever latest available public for free macos-12 agents.
OS of the machine running the runner? OSX/Windows/Linux/...
macos-12
What's not working?
We try to run minikube with Virtualbox but it fails because it gives us M1 Machines (arm64) and virtualbox only runs on intel.
Currently we are trying to implement a workaround that if we detect the CPU arch to be arm64 we Exit the test so at least it doenst fail, and we are planning to implement a cron job to keep triggering the test till it Gets the Right architecture, which is just a hack to get us going, and this is affecting anyone who uses macos runners, it is better to be fixed in github action runner for all users.