[SERVER-30578] resmoke should not start more servers than there are tests to perform Created: 09/Aug/17 Updated: 30/Oct/23 Resolved: 07/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.13 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | TIG 2017-09-11, TIG 2017-10-02 |
| Participants: |
| Description |
|
When you go from "resmoke --suite=SUITE -j12" to "resmoke --suite=SUITE jstests/THE/FAILING/TEST.js" is it easy to forget to remove the -j12. The causes resmoke to spend a lot of extra time starting up servers/clusters that will never be used. This can also happen if SUITE has fewer tests than the -j value. |
| Comments |
| Comment by Githook User [ 07/Sep/17 ] |
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}Message: |