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

Enable testing arm64 Mac architecture in the CI. #3422

Merged
merged 4 commits into from
Sep 23, 2024

Conversation

h-mayorquin
Copy link
Collaborator

Moving forward with #3100.

@h-mayorquin h-mayorquin marked this pull request as ready for review September 18, 2024 02:42
@h-mayorquin h-mayorquin self-assigned this Sep 18, 2024
@h-mayorquin h-mayorquin added testing Related to test routines continuous integration Related to CI labels Sep 18, 2024
@h-mayorquin
Copy link
Collaborator Author

Uh, that's great, it just... worked.

@h-mayorquin h-mayorquin changed the title Add macos latest to test Enable testing arm64 Mac architecture in the CI. Sep 18, 2024
@h-mayorquin
Copy link
Collaborator Author

Ah, of course it was so easy, we did not have logic for running everything if the workflow files from github actions are changed. I added that.

@h-mayorquin
Copy link
Collaborator Author

Ok, this is ready. I also eliminated a warning from the CI to keep things tidy 🧹 🧹 🧹 ( x D )

@zm711
Copy link
Collaborator

zm711 commented Sep 18, 2024

I think the only potentially slow step would be if we do a bunch of torch things, since pytorch defaults to the Mac CPU instead of GPU, but I don't even know what the runner GPU story is.

version.parse(platform.python_version()) >= version.parse("3.10"),
reason="Sonpy only testing with Python < 3.10!",
version.parse(platform.python_version()) >= version.parse("3.10") or platform.system() == "Darwin",
reason="Sonpy only testing with Python < 3.10 and not supported on macOS!",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this an Arm issue?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, want to give it a shot to have something that excludes intel cpus from mac? I think they stopped selling two years ago only so many people might still have them.

That said, I did not want to allocate extra effort to something that won't work in a year anyway (see the python restriction)

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think that's fair. Let's not waste effort. our new Neo deprecation policy will also hit this one eventually.

Copy link
Collaborator

@zm711 zm711 left a comment

Choose a reason for hiding this comment

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

For me this is good to go. Based on a google intel Macs officially went end of life in JUNE2024. So only testing on officially supported hardware seems fair to me. And it looks like it successfully tested everything for complete tests so I think this should be good to go.

@alejoe91 alejoe91 merged commit 9d7832c into SpikeInterface:main Sep 23, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
continuous integration Related to CI testing Related to test routines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants