ci: faster, stricter CI (instrumented gate, parallel jobs, test forks) (#1348)

This commit is contained in:
m57 authored and GitHub committed 2026-09-28 00:20:52 +03:00
1 parent 2a41a8a417
commit d81fc39f25
6 files changed
+58 -19

No files matched your search

@@ -2188,12 +2188,13 @@ class HermesWsClientTest {
val failureLatch = CountDownLatch(1)
HermesWsClient.probeLivenessOnTransportChange(
timeoutMs = 50L,
onFailureAction = {
failureLatch.countDown()
},
)
assertTrue("Expected failure action to be invoked on failed ping", failureLatch.await(6, TimeUnit.SECONDS))
assertTrue("Expected failure action to be invoked on failed ping", failureLatch.await(3, TimeUnit.SECONDS))
}
@Test
@@ -412,16 +412,23 @@ class NotificationReplyReceiverTest {
kotlinx.coroutines.delay(10000)
}
receiver.onReceive(mockContext, mockIntent)
// Same timeout path as production, with a short deadline instead of 5s.
val shortTimeoutReceiver =
object : NotificationReplyReceiver() {
override fun goAsyncCompat(): BroadcastReceiver.PendingResult = mockPendingResult
// Wait longer than the 5-second timeout, but less than the 10-second delay
Thread.sleep(6000)
override fun buildReplyNotification(context: Context): Notification = mockNotification
override val persistenceTimeoutMs: Long = 50L
}
shortTimeoutReceiver.onReceive(mockContext, mockIntent)
// Timeout should be caught in catch block and logged
verify { android.util.Log.e("NotificationReply", any<String>(), any()) }
verify(timeout = 3_000) { android.util.Log.e("NotificationReply", any<String>(), any()) }
// Pending result must still finish after timeout
verify { mockPendingResult.finish() }
verify(timeout = 3_000) { mockPendingResult.finish() }
}
// ── Helpers ────────────────────────────────────────────────────────────