Uploaded image for project: 'Realm Core'
  1. Realm Core
  2. RCORE-1394

Metrics_TransactionTimings sometimes fails with "failed with (0, 0)"

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Core
    • None

      Update the Metrics_TransactionTimings test to look for greater than or equal instead of greater than, since the test sometimes fails with CHECK_GREATER(transactions->at(3).get_fsync_time_nanoseconds(), 0) failed with (0, 0) even though the test was successful.

      Example: https://spruce.mongodb.com/task/realm_core_stable_windows_64_vs2019_release_core_tests_patch_818562016f7a903d9f72a571d995b17661f39432_63b48d167742ae0d50be99d2_23_01_03_20_16_22/logs?execution=0&sortBy=STATUS&sortDir=ASC

      [2023/01/03 20:33:49.231] 1: Thread[5]: C:\data\mci\11bdcc3981b6923fd2593d36de84f8b2\realm-core\test\test_metrics.cpp:722: Begin Metrics_TransactionTimings
[2023/01/03 20:33:49.397] 1: Thread[5]: C:\data\mci\11bdcc3981b6923fd2593d36de84f8b2\realm-core\test\test_metrics.cpp:799: ERROR in Metrics_TransactionTimings: CHECK_GREATER(transactions->at(3).get_fsync_time_nanoseconds(), 0) failed with (0, 0)

            Assignee:
            Unassigned Unassigned
            Reporter:
            michael.wilkersonbarker@mongodb.com Michael Wilkerson-Barker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: