[SERVER-67981] Tests that timeout and not using mongobridge in catalog shard POC Created: 11/Jul/22 Updated: 05/Dec/22 Resolved: 04/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding NYC |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding NYC
|
| Sprint: | Sharding 2022-10-17 |
| Participants: | |
| Story Points: | 3 |
| Description |
|
There are many tests that timeout, it is unknown how many root causes could be. I am not listing any particular test to not group them together. This ticket excludes tests that are using mongobridge. It would be better if only one person looks at timeouts. When a root cause is found and fixed - please rename this ticket. If there are still other tests timing out - file a new ticket. |