[SERVER-80327] Investigate potential pre-image test issue with small time values Created: 23/Aug/23 Updated: 29/Oct/23 Resolved: 07/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Yujin Kang Park | Assignee: | Yujin Kang Park |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution EMEA Team 2023-09-18 |
| Participants: |
| Description |
|
Timestamps where the seconds part is 0 are considered null. Tests using mock clocks start with 0 or rather small values, which might change the behaviour of the code being tested, due to generating Timestamp objects from a Date_t generated from the clock. This turned out to be an issue with change collections expiration testing ( |
| Comments |
| Comment by Githook User [ 06/Sep/23 ] |
|
Author: {'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}Message: |