Accuracy bounds are too tight in t-digest unit tests

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • QI 2023-04-03
    • 43
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Because we generate the data on the fly, the accuracy bounds might be violated now and then. While it's valuable to keep an eye on this, failing unit tests create too much friction. We should freeze the seed and test for accuracy in some other way.

            Assignee:
            Irina Yatsenko (Inactive)
            Reporter:
            Irina Yatsenko (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: