[SERVER-38054] failCommand fail point causes errors when run concurrently with other tests Created: 09/Nov/18 Updated: 29/Oct/23 Resolved: 13/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Natalie Tsvetkova | Assignee: | Natalie Tsvetkova |
| 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: | Sharding 2018-11-19 | ||||
| Participants: | |||||
| Linked BF Score: | 10 | ||||
| Description |
|
The failcommand_failpoint.js test puts a failpoint on find as part of the testing. When it is run in parallel with certain suites that also use find in their tests, it can cause both the tests to fail. In this case, failcommand_failpoint.js has to be added to the blacklists of replica_sets_kill_secondaries_jscore_passthrough and replica_sets_initsync_jscore_passthrough. Alternatively, we could use similar logic to what the checkForInterrupt failpoint does (https://github.com/mongodb/mongo/blob/r4.1.4/src/mongo/db/operation_context.cpp#L172-L215, https://github.com/mongodb/mongo/blob/r4.1.4/jstests/libs/jstestfuzz/check_for_interrupt_hook.js#L18-L22). |
| Comments |
| Comment by Githook User [ 13/Nov/18 ] |
|
Author: {'name': 'Natalie Tsvetkova', 'email': 'natalie.tsvetkova@mongodb.com', 'username': 'ntsvetko'}Message: |