[SERVER-45925] Disable incremental_backup_cursor.js temporarily Created: 03/Feb/20 Updated: 29/Oct/23 Resolved: 03/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| 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 | ||||
| Sprint: | Execution Team 2020-02-10 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
There's a bug inside of the WT library, specifically with api_enter_refcnt. Because of this, the bug causes the thread id to not clear and we end up hitting a WT error later down the road because of thread id checks.
We should disable this test as it's failing often until the next WT drop which will fix this bug. |
| Comments |
| Comment by Githook User [ 03/Feb/20 ] |
|
Author: {'username': 'GWlodarek', 'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com'}Message: |