[SERVER-36940] Remove assertion that we find exactly one session in multi_statement_transaction_kill_sessions.js Created: 30/Aug/18 Updated: 29/Oct/23 Resolved: 10/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2018-09-24 | ||||
| Participants: | |||||
| Linked BF Score: | 41 | ||||
| Description |
|
In this workload, we run listSessions but exclude our own session from the results. Thus, it is possible to not return a session and fail the assertion here. We should instead check if we've found a session, and if not simply do nothing. |
| Comments |
| Comment by Githook User [ 10/Sep/18 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: |