[SERVER-85924] Remove profiling tests from fcv upgrade downgrade passthrough suites Created: 30/Jan/24 Updated: 30/Jan/24 Resolved: 30/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 5 | ||||||||||||
| Description |
|
Profiling tests in jsCore that configure the database profiler may cause slow setFeatureCompatibilityVersion operations in the fcv upgrade downgrade suite to create unexpected system.profile collections in test databases, potentially throwing off test assertions that rely on a certain collection catalog state. We have seen a number of such test failures in our CI system and should consider excluding some of these profiling tests. Similar changes were done in |
| Comments |
| Comment by Steven Vannelli [ 30/Jan/24 ] |
|
Closing out in favor of |