NNAPI VTS: use max time point instead of uint64_t max

Bug: 149441015
Test: mma
Test: VtsHalNeuralnetworksV1_3TargetTest
Change-Id: Ic74f83242cbe04a4cec47adbfc51002fdf8bb47d
Merged-In: Ic74f83242cbe04a4cec47adbfc51002fdf8bb47d
(cherry picked from commit 79d6bb1ad2)
This commit is contained in:
Michael Butler 2020-02-12 18:54:07 -08:00 committed by Slava Shklyaev
parent 17689aa67d
commit 36902cbc2f

View file

@ -67,8 +67,10 @@ static OptionalTimePoint makeOptionalTimePoint(DeadlineBoundType deadlineBoundTy
deadline.nanosecondsSinceEpoch(nanosecondsSinceEpoch);
} break;
case DeadlineBoundType::UNLIMITED: {
uint64_t unlimited = std::numeric_limits<uint64_t>::max();
deadline.nanosecondsSinceEpoch(unlimited);
const auto maxTime = std::chrono::time_point<std::chrono::steady_clock,
std::chrono::nanoseconds>::max();
const uint64_t nanosecondsSinceEpoch = maxTime.time_since_epoch().count();
deadline.nanosecondsSinceEpoch(nanosecondsSinceEpoch);
} break;
}
return deadline;