[SERVER-86213] timeseries_bucket_limit_count.js may have different bucketing than expected if it runs slowly Created: 05/Feb/24  Updated: 06/Feb/24  Resolved: 06/Feb/24

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

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
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
Operating System: ALL
Sprint: Execution Team 2024-02-19
Participants:
Linked BF Score: 147

 Description   

Since this test uses a new timestamp for each document, if it runs slowly enough then the bucket may roll over due to time forward.



 Comments   
Comment by Githook User [ 06/Feb/24 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-86213 Use consistent time in `timeseries_bucket_limit_count.js` (#18705)

GitOrigin-RevId: 49e18c8fc4dac6e6e50d44e770bce495e13683f7
Branch: master
https://github.com/mongodb/mongo/commit/a0f4afdfe2d3d4e8b38014984e8ddde0fc79f753

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