Camera2 CTS: Fix too-low timeout in AllocationTest#testBlackWhite
A fixed 5-second timeout isn't long enough when dealing with devices
that support long exposure.
Ideally the timeout would be calculated based on the requested
exposure time, but for simplicity, simply increase it to 20 seconds.
Test: CTS test now passes on a device supporting ~4 second exposures
Bug: 38212789
Change-Id: Ib5f0840e341490bca2472fa243b5649224975d4a
diff --git a/tests/camera/src/android/hardware/camera2/cts/rs/BlockingInputAllocation.java b/tests/camera/src/android/hardware/camera2/cts/rs/BlockingInputAllocation.java
index 0305540..c7435a8 100644
--- a/tests/camera/src/android/hardware/camera2/cts/rs/BlockingInputAllocation.java
+++ b/tests/camera/src/android/hardware/camera2/cts/rs/BlockingInputAllocation.java
@@ -164,7 +164,7 @@
private static class OnBufferAvailableListener implements Allocation.OnBufferAvailableListener {
private int mPendingBuffers = 0;
private final Object mBufferSyncObject = new Object();
- private static final int TIMEOUT_MS = 5000;
+ private static final int TIMEOUT_MS = 20000;
public boolean isBufferPending() {
synchronized (mBufferSyncObject) {
