From e4a6153d08c4fe36446280072495a84699ff449b Mon Sep 17 00:00:00 2001 From: Junyu Lai Date: Wed, 7 Jun 2023 10:31:11 +0800 Subject: [PATCH] Add more log when Range misconfigured Currently, when lower/upper bound of Range is incorrect, there is no useful information for debugging. Test: atest TrafficStatsTest Bug: 285452306 Change-Id: I0e390692c20b37e14958ecc0fd45c93f73fe63e2 --- tests/cts/net/src/android/net/cts/TrafficStatsTest.java | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tests/cts/net/src/android/net/cts/TrafficStatsTest.java b/tests/cts/net/src/android/net/cts/TrafficStatsTest.java index 1d9268ae11..bd9e03c2bd 100755 --- a/tests/cts/net/src/android/net/cts/TrafficStatsTest.java +++ b/tests/cts/net/src/android/net/cts/TrafficStatsTest.java @@ -37,6 +37,9 @@ public class TrafficStatsTest extends AndroidTestCase { /** Verify the given value is in range [lower, upper] */ private void assertInRange(String tag, long value, long lower, long upper) { + if (lower > upper) { + fail("lower must be less than or equal to upper: [" + lower + "," + upper + "]"); + } final Range range = new Range(lower, upper); assertTrue(tag + ": " + value + " is not within range [" + lower + ", " + upper + "]", range.contains(value));