Reduce the number of iterations in PreEnrollTest
The current number of iterations is too high and results in a timeout from the testing framework. The goal of the test is to make sure that the generated challenges are different on every run. It's impossible to test whether any two challenges will ever be the same for any number of iterations. Hence, since a 1000 iterations doesn't provide much more value over 10 iterations, 10 was chosen because of its better performance. Bug: 155844206 Test: "atest VtsHalBiometricsFingerprintV2_1TargetTest" on a blueline Change-Id: I5db887bdcfed8fb0e44fcedcf9e99dd185d395c3
This commit is contained in:
parent
ac4ee96268
commit
744b028807
1 changed files with 1 additions and 1 deletions
|
@ -49,7 +49,7 @@ static const uint32_t kTimeout = 3;
|
||||||
static const std::chrono::seconds kTimeoutInSeconds = std::chrono::seconds(kTimeout);
|
static const std::chrono::seconds kTimeoutInSeconds = std::chrono::seconds(kTimeout);
|
||||||
static const uint32_t kGroupId = 99;
|
static const uint32_t kGroupId = 99;
|
||||||
static std::string kTmpDir = "";
|
static std::string kTmpDir = "";
|
||||||
static const uint32_t kIterations = 1000;
|
static const uint32_t kIterations = 10;
|
||||||
|
|
||||||
// Wait for a callback to occur (signaled by the given future) up to the
|
// Wait for a callback to occur (signaled by the given future) up to the
|
||||||
// provided timeout. If the future is invalid or the callback does not come
|
// provided timeout. If the future is invalid or the callback does not come
|
||||||
|
|
Loading…
Reference in a new issue