[SERVER-63158] shell_hang_analyzer.js test fails assert.soon & calls hang again Created: 31/Jan/22 Updated: 29/Oct/23 Resolved: 25/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tausif Rahman (Inactive) | Assignee: | Tausif Rahman (Inactive) |
| 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: | STM 2022-03-07 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Story Points: | 1 | ||||
| Description |
|
shell_hang_analyzer.js tests the hang analyzer by starting a dummy mongod process and killing it. In BF-24186, we expected the dummy process to be dead and we usedĀ this assert.soon which fails. At this point we should just fail the test, but due to the way assert.soon works, the hang analyzer gets called on all processes if assert.soon fails. In this case, we unnecessarily call the hang analyzer on an unrelated sharded cluster fixture & result in a test timeout. We should pass in theĀ {runHangAnalyzer = false} argument as described here to prevent running the hang analyzer on the unrelated sharded cluster fixture in this scenario. |
| Comments |
| Comment by Githook User [ 25/Feb/22 ] |
|
Author: {'name': 'trahman1318', 'email': 'tausif.rahman@mongodb.com', 'username': 'trahman1318'}Message: |