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

Add aarch64-android testing to CI #116

Closed

Conversation

afranchuk
Copy link
Contributor

Let's see if this works... I didn't try locally testing aarch64-android because I didn't want to jump through hoops to install the aarch64 qemu and get that working (Google dropped support so it doesn't Just Work).

@afranchuk
Copy link
Contributor Author

I am absolutely blown away that GitHub doesn't document what CPU architecture their runners use. The aarch64 test is hanging for the same reason I can't run locally; I assumed the Action I'm using would do the right thing.

@afranchuk afranchuk force-pushed the android-aarch64-testing branch 2 times, most recently from 97217a7 to fb2e124 Compare April 11, 2024 14:37
@afranchuk
Copy link
Contributor Author

Due to ReactiveCircus/android-emulator-runner#350, the only aarch64(ish) github actions platform, macos-14, doesn't work. We can't test aarch64-android without an aarch64 runner.

@afranchuk afranchuk closed this Apr 11, 2024
@Jake-Shadle
Copy link
Collaborator

Well that's extremely unfortunate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants