[SERVER-75402] Accuracy bounds are too tight in t-digest unit tests Created: 28/Mar/23  Updated: 29/Oct/23  Resolved: 29/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Irina Yatsenko (Inactive) Assignee: Irina Yatsenko (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: QI 2023-04-03
Participants:
Linked BF Score: 43

 Description   

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.



 Comments   
Comment by Githook User [ 29/Mar/23 ]

Author:

{'name': 'Irina Yatsenko', 'email': 'irina.yatsenko@mongodb.com', 'username': 'IrinaYatsenko'}

Message: SERVER-75402 Freeze the seed when generating data for t-digest tests
Branch: master
https://github.com/mongodb/mongo/commit/b5a27b4530a84165c6f86b67140a1f1cef061cfe

Generated at Thu Feb 08 06:30:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.