[SERVER-25363] Split up slow1 test suite Created: 29/Jul/16 Updated: 06/Dec/22 Resolved: 11/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.3.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Grundy | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | PM424, stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Tooling & Methods
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The slow1 test suite has been suffering from out of memory kills. The problem is some of the tests shouldn't be run concurrently because they are starting their own shardingtest harnesses. At one point while debugging I counted 18 mongod processes and two mongos. |
| Comments |
| Comment by Ryan Timmons [ 11/May/20 ] | |||||||||||||||||||||
|
Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue. | |||||||||||||||||||||
| Comment by Michael Grundy [ 01/Aug/16 ] | |||||||||||||||||||||
|
Some of the tests in slow1 start their own fixtures. I've outlined each test's behavior below:
We should probably split this into two suites, one that starts fixtures and one that doesn't. mr_during_migrate.js may need to be moved to the serial suite. |