Fix start info clock tests
Both of these tests are flaky due to how quickly the test can run, resulting in the clock not actually advancing as expected. For the ordering test, add a 1ms delay between timestamps thereby guaranteeing that the time advances. For the persistence test, change the check to include equals as a valid pass case. This is ok because it still ensures that the clock was loaded from disk rather than being initialized as new. Test: run each test 15 times, all pass Bug: 361874703 Flag: EXEMPT - test fix Change-Id: I17b0612795b6ffceaaff60c975a951202a6272e4
Loading
Please register or sign in to comment