[SERVER-18617] resmoke.py should not error when attempting to tear down fixtures which have not been set up. Created: 21/May/15 Updated: 19/Sep/15 Resolved: 22/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.1.3 |
| Fix Version/s: | 3.1.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Quint Iteration 4 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
If for any reason setting up a fixture fails, it will not call setup() on the rest of the fixtures, but will call teardown() on them. In the case of a MongoDFixture or a MongoSFixture, this will result in attempting to log the port, which hasn't been assigned yet. It should just not log anything if it had never been set up. |
| Comments |
| Comment by Githook User [ 22/May/15 ] |
|
Author: {u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}Message: |