[SERVER-22198] resmoke.py should obey order of tests specified via command line Created: 15/Jan/16 Updated: 21/Nov/16 Resolved: 28/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.7, 3.3.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Michael Grundy |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Sprint: | TIG 12 (04/01/16), TIG 13 (04/22/16), TIG 14 (05/13/16) |
| Participants: |
| Description |
|
If --shuffle was not passed to resmoke.py, and you specified more than one test via the command line, then we should run the tests in the order specified. For example
Should run where2.js, then find1.js, then explain1.js. Of course, if you're running with multiple jobs, the best it can do is to put them in the queue in that order. It looks like the order isn't preserved because the logic in buildscripts/resmokelib/selector.py uses a set to compute which tests should be run, losing the original order. |
| Comments |
| Comment by Githook User [ 16/May/16 ] |
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: (cherry picked from commit e7e0ef104b8266d0dbd786c8bb4e8e8b77c8f0e6) |
| Comment by Githook User [ 28/Apr/16 ] |
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: |