From ce5b6dda356f6ad1af5ca398bae0dede51592648 Mon Sep 17 00:00:00 2001
From: Joe Onorato <joeo@google.com>
Date: Fri, 26 May 2017 20:04:00 -0700
Subject: [PATCH] Turn off the check in the test because the assertion is off
 in the implementation.

Bug: 38350004
Test: bit FrameworksCoreTests:com.android.internal.app.procstats.SparseMappingTableTest
Change-Id: I4b58610fd1ac9ca082479a7d5ba40c69f0a26654
---
 .../internal/app/procstats/SparseMappingTableTest.java        | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/core/tests/coretests/src/com/android/internal/app/procstats/SparseMappingTableTest.java b/core/tests/coretests/src/com/android/internal/app/procstats/SparseMappingTableTest.java
index fd57baa217b0f..115af5e0ea5d5 100644
--- a/core/tests/coretests/src/com/android/internal/app/procstats/SparseMappingTableTest.java
+++ b/core/tests/coretests/src/com/android/internal/app/procstats/SparseMappingTableTest.java
@@ -180,7 +180,9 @@ public class SparseMappingTableTest extends TestCase {
 
         try {
             table.getValue(key);
-            throw new Exception("Exception not thrown after mismatched reset calls.");
+            // Turn off this assertion because the check in SparseMappingTable.assertConsistency
+            // is also turned off.
+            //throw new Exception("Exception not thrown after mismatched reset calls.");
         } catch (RuntimeException ex) {
             // Good
         }