From 22d23db00c5d583f77ce7a07e40b3dbec1b1e663 Mon Sep 17 00:00:00 2001 From: Daniel McCarney Date: Tue, 12 Mar 2024 13:56:18 -0400 Subject: [PATCH] ci: use default Android emulator target Previously the Android emulator based CI job was using the larger `googles_api` target instead of the slimmer default. This was done to ensure network access worked as intended for the real-world test suite with a TODO to revisit after an upstream bug was fixed. In the meantime the upstream bug has been closed and we've upgraded the emulator action version. Let's try the default target again and hopefully get a small CI speedup. --- .github/workflows/ci.yml | 7 ------- 1 file changed, 7 deletions(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 385a8c2a..9ba1f2ba 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -144,13 +144,6 @@ jobs: api-level: 28 # Android 9, Pie. arch: x86_64 profile: pixel - # Note: We use the `google_apis` target because the default one doesn't have access to - # the internet for the real-world test suite. The intermediate certificate doesn't have - # stapled revocation data, so the system must look it up instead. - # - # This can use the default target (which is less bloated) once - # https://github.com/ReactiveCircus/android-emulator-runner/issues/220 is resolved. - target: google_apis emulator-options: -no-snapshot-save -no-window -gpu swiftshader_indirect -noaudio -no-boot-anim -camera-back none disable-animations: true working-directory: ./android