Increase TEST_TIMEOUT_MS to 30s in the IpClientTest.
Generally TEST_TIMEOUT_MS constant is used to wait particular event
to happen or verify API to be invoked. So far this constant is 400ms,
probably that is not long enough on certain test platform. updating
it to 30s in unit test doesn't increase the entire test duration.
Bug: 202548741
Test: atest NetworkStackTests NetworkStackNextTests
Change-Id: I89f8f4752f9edc6246ea8d998ef26459b25801a9
diff --git a/tests/unit/src/android/net/ip/IpClientTest.java b/tests/unit/src/android/net/ip/IpClientTest.java
index 95fe93a..a37d259 100644
--- a/tests/unit/src/android/net/ip/IpClientTest.java
+++ b/tests/unit/src/android/net/ip/IpClientTest.java
@@ -110,7 +110,7 @@
private static final int TEST_IFINDEX = 1001;
// See RFC 7042#section-2.1.2 for EUI-48 documentation values.
private static final MacAddress TEST_MAC = MacAddress.fromString("00:00:5E:00:53:01");
- private static final int TEST_TIMEOUT_MS = 400;
+ private static final int TEST_TIMEOUT_MS = 30_000;
private static final String TEST_L2KEY = "some l2key";
private static final String TEST_CLUSTER = "some cluster";
private static final String TEST_SSID = "test_ssid";