[SERVER-46034] flake: deadline of `now` fails intermittently Created: 07/Feb/20 Updated: 29/Oct/23 Resolved: 10/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Billy Donahue | Assignee: | Billy Donahue |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | build/static_gcc_ninja/mongo/db/db_unittests --suite=DBRAIITestFixture --filter=AutoGetCollectionForReadGlobalLockDeadline |
||||||||||||
| Sprint: | Dev Tools 2020-02-10 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
Test is acquiring GlobalLock with deadline of `now()`. This is wrong but will succeed if the acquisition is fast and lucky enough that it can all be done in the same wallclock millisecond. In Debug builds, it fails more often because debug-only lock diagnostics make the acquisition slower, so it crosses a millisecond boundary more often and fails. flaky red herring found while debugging |
| Comments |
| Comment by Githook User [ 10/Feb/20 ] |
|
Author: {'name': 'Billy Donahue', 'username': 'BillyDonahue', 'email': 'billy.donahue@mongodb.com'}Message: |
| Comment by Billy Donahue [ 07/Feb/20 ] |