From f1c0ed7b05481e75de4c527dba4b053c0f584001 Mon Sep 17 00:00:00 2001 From: Andy Scherzinger Date: Mon, 12 Oct 2026 08:37:42 +0200 Subject: [PATCH] fix(tests): run the display cutout test on the same SDK as the others `DisplayCutoutPaddingTest` is the only Robolectric test in the suite pinned to SDK 31; the other twelve all run on 33. That makes the run fetch a second `android-all` jar, and the download of that one has been failing on CI since the test landed, taking the whole suite down with it in `initializationError` before any assertion runs. Nothing in the test depends on 31. Window insets are dispatched the same way on both levels, so the behaviour under test is unchanged. Assisted-by: Claude Code:claude-opus-5 Signed-off-by: Andy Scherzinger --- .../java/com/nextcloud/talk/utils/DisplayCutoutPaddingTest.kt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/test/java/com/nextcloud/talk/utils/DisplayCutoutPaddingTest.kt b/app/src/test/java/com/nextcloud/talk/utils/DisplayCutoutPaddingTest.kt index 12f208b83b..aebe8e2085 100644 --- a/app/src/test/java/com/nextcloud/talk/utils/DisplayCutoutPaddingTest.kt +++ b/app/src/test/java/com/nextcloud/talk/utils/DisplayCutoutPaddingTest.kt @@ -24,7 +24,7 @@ import org.robolectric.annotation.Config * must be padded by the cutout, otherwise it is drawn below the camera. */ @RunWith(RobolectricTestRunner::class) -@Config(application = Application::class, sdk = [31]) +@Config(application = Application::class, sdk = [33]) class DisplayCutoutPaddingTest { private fun dispatch(view: FrameLayout, cutout: Insets) {