From 5eb5b16bb978ae5cb54ba1aa60941ed79a54ecc8 Mon Sep 17 00:00:00 2001 From: Mike Hardy Date: Tue, 14 May 2024 16:17:21 -0500 Subject: [PATCH] test(ci, android): only run one emulator test at once the idea of having an exercise of android emulator at our lowest supported API is temping, but it has not been stable in practice --- .github/workflows/tests_e2e_android.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/tests_e2e_android.yml b/.github/workflows/tests_e2e_android.yml index 06c6fc2056..2afca7442f 100644 --- a/.github/workflows/tests_e2e_android.yml +++ b/.github/workflows/tests_e2e_android.yml @@ -38,7 +38,8 @@ jobs: # 23-25, 28-29 appears to work locally but fails in CI # 26 does not support performance tracing due to hardware acceleration bugs # min-possible + max-possible skew looks like 29 and 34 then - api-level: [30, 34] + # running anything below 34 fails at the moment though, so using only it for now + api-level: [34] arch: [x86_64] target: [google_apis] # This is useful for benchmarking, do 0, 1, 2, etc (up to 256 max job-per-matrix limit) for averages