[SERVER-21421] Update concurrency suite's ThreadManager constructor to provide default executionMode Created: 12/Nov/15 Updated: 18/Nov/16 Resolved: 19/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.2.0-rc2 |
| Fix Version/s: | 3.2.3, 3.3.1 |
| Type: | Task | Priority: | Trivial - P5 |
| Reporter: | Kamran K. | 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 |
| Backport Completed: | |
| Sprint: | TIG E (01/08/16), TIG F (01/29/16) |
| Participants: |
| Description |
|
The ThreadManager constructor in jstests/concurrency/fsm_libs/thread_mgr.js should not require that you pass an explicit executionMode parameter. Instead, it can just provide a default value to simplify calling code. |
| Comments |
| Comment by Githook User [ 25/Jan/16 ] |
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: (cherry picked from commit 23a61625841080dae2cf0e07e7aadad0e1424722) |
| Comment by Githook User [ 19/Jan/16 ] |
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: |