background_thread_clock_source_test shouldn't assume we can schedule the background thread

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • v4.2
    • Service Arch 2019-07-01, Service Arch 2019-07-15
    • 14
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      BF-12646 shows that sometimes we can fail to schedule the background thread clock source for >100ms (or that time moves backwards).

      I believe the fix here is to change the ASSERT_GT to a ASSERT_GTE (to account for failures to schedule)

              Assignee:
              Shaileja Jain (Inactive)
              Reporter:
              Mira Carey
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: