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

gh: Stop using macos11 runners #164

Merged
merged 2 commits into from
Aug 29, 2024
Merged

Conversation

cfergeau
Copy link
Collaborator

@cfergeau cfergeau commented Jul 10, 2024

This removes the macos11 usage from github actions, and starts using macos14
macos11 runners are deprecated or removed from github actions:
https://github.blog/changelog/2024-05-20-actions-upcoming-changes-to-github-hosted-macos-runners/

Copy link

openshift-ci bot commented Jul 10, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from cfergeau. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@praveenkumar
Copy link
Member

The test around macOS-14 is failing now.

@cfergeau
Copy link
Collaborator Author

The test around macOS-14 is failing now.

Yes it's being run on an arm64 node which can't do virt, so it's unfortunately an expected failure. I haven't found a way to force the run to be done on an amd64/macos14 node.

@praveenkumar
Copy link
Member

The test around macOS-14 is failing now.

Yes it's being run on an arm64 node which can't do virt, so it's unfortunately an expected failure. I haven't found a way to force the run to be done on an amd64/macos14 node.

I don't think the runner for macos14 have intel one in the background only silicon available https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources which is on M1 (no virt support) . We either tweak the test case to run it on M1 or just don't add macOS-14 support for action.

This removes the macos11 usage from github actions.
macos11 runners are deprecated or removed from github actions:
https://github.blog/changelog/2024-05-20-actions-upcoming-changes-to-github-hosted-macos-runners/

Signed-off-by: Christophe Fergeau <[email protected]>
`make test` is not run on macOS 14 runners as they don't support nested
virtualization.

Signed-off-by: Christophe Fergeau <[email protected]>
@cfergeau
Copy link
Collaborator Author

cfergeau commented Aug 22, 2024

The test around macOS-14 is failing now.

Yes it's being run on an arm64 node which can't do virt, so it's unfortunately an expected failure. I haven't found a way to force the run to be done on an amd64/macos14 node.

I don't think the runner for macos14 have intel one in the background only silicon available https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources which is on M1 (no virt support) . We either tweak the test case to run it on M1 or just don't add macOS-14 support for action.

I disabled the tests on macOS14. The tests in test/ require virtualization as they start a VM and check that the VM has the expected configuration. The other tests in pkg/ are unit tests and could be run without virt. Might be worth splitting them in make unit-tests and make e2e-tests so that we can run a few more tests on macOS 14

@praveenkumar
Copy link
Member

Does this need rebase becuase lint is failing and using (1.60.2) ?

@cfergeau
Copy link
Collaborator Author

Does this need rebase becuase lint is failing and using (1.60.2) ?

lint is a mess at the moment, better to ignore it :-/

@cfergeau
Copy link
Collaborator Author

Does this need rebase becuase lint is failing and using (1.60.2) ?

lint is a mess at the moment, better to ignore it :-/

The lint issues are fixed in #185

@praveenkumar praveenkumar merged commit a638243 into crc-org:main Aug 29, 2024
3 of 6 checks passed
@praveenkumar praveenkumar mentioned this pull request Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants