Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9f0cbb6a authored by Rahul Arya's avatar Rahul Arya
Browse files

Remove timing-dependent unit test 

Doesn't make sense to have such specific timing requirements in a unit test running in an unknown environment.

Fixes: 249245228
Change-Id: I2c90892e6c6ecaf130efb5e5ba68c37b876250fd
Test: gd unit
parent 10dde119

system/gd/common/lru_cache_test.cc

+0 −9
Original line number Diff line number Diff line
@@ -14,7 +14,6 @@ 
 * limitations under the License.

 */



#include <chrono>

#include <limits>



#include <gmock/gmock.h>
@@ -419,7 +418,6 @@ TEST(LruCacheTest, for_loop_test) { 
}



TEST(LruCacheTest, pressure_test) {

  auto started = std::chrono::high_resolution_clock::now();

  int capacity = 0xFFFF;  // 2^16 = 65535

  LruCache<int, int> cache(static_cast<size_t>(capacity));
@@ -449,13 +447,6 @@ TEST(LruCacheTest, pressure_test) { 
    EXPECT_TRUE(cache.extract(key));

  }

  EXPECT_EQ(cache.size(), 0ul);



  // test execution time

  auto done = std::chrono::high_resolution_clock::now();

  int execution_time = std::chrono::duration_cast<std::chrono::microseconds>(done - started).count();

  // Shouldn't be more than 1120ms

  int execution_time_per_cycle_us = 17;

  EXPECT_LT(execution_time, execution_time_per_cycle_us * capacity);

}



}  // namespace testing