Michael Eischer 99547518cd lock: fix flaky TestLockFailedRefresh ... The comparison of the current time and the last lock refresh were using seconds represented as integers. As the test only waits for up to one second, the associated number truncation can cause the test to take longer than once second and thus to fail. Switch to nanoseconds to avoid this problem. This also slightly speeds up the test.		2022-10-15 22:36:32 +02:00
..
restic	lock: fix flaky TestLockFailedRefresh	2022-10-15 22:36:32 +02:00