[SERVER-43186] Limit the number of tests added to a generated suite Created: 05/Sep/19 Updated: 29/Oct/23 Resolved: 06/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.13, 4.2.1, 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.2, v4.0
|
||||||||
| Sprint: | DAG 2019-09-09 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
The "CleanEveryN" test hook gets run every "N" tests. Due to the way tests are run, this could be run against a different test every execution. This means that when we use test runtime to calculate timeouts, we might not properly account for the "CleanEveryN" runtime and set a timeout too short. This is most problematic on suites made up of lots of short running tests. If we had a maximum number of tests per suite we used when dividing the tests up, this would no longer be a problem. As a server engineer, AC:
|
| Comments |
| Comment by Githook User [ 09/Sep/19 ] |
|
Author: {'name': 'David Bradford', 'username': 'dbradf', 'email': 'david.bradford@mongodb.com'}Message: (cherry picked from commit cdf0a059437f1ed417a22b3c574e2f73afc04233) |
| Comment by Githook User [ 06/Sep/19 ] |
|
Author: {'name': 'David Bradford', 'username': 'dbradf', 'email': 'david.bradford@mongodb.com'}Message: (cherry picked from commit cdf0a059437f1ed417a22b3c574e2f73afc04233) |
| Comment by Githook User [ 06/Sep/19 ] |
|
Author: {'username': 'dbradf', 'email': 'david.bradford@mongodb.com', 'name': 'David Bradford'}Message: |