[SERVER-22195] queryoptimizer3.js failing on 2.6 Created: 07/Jan/16 Updated: 22/Mar/16 Resolved: 15/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.12 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | David Storch | Assignee: | James Wahlin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Major Change | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Query F (02/01/16) | ||||||||
| Participants: | |||||||||
| Description |
|
Looks like this was introduced with the backport of |
| Comments |
| Comment by Githook User [ 15/Jan/16 ] |
|
Author: {u'username': u'jameswahlin', u'name': u'James Wahlin', u'email': u'james.wahlin@10gen.com'}Message: |
| Comment by David Storch [ 14/Jan/16 ] |
|
I don't think we should remove the test. We don't have a lot of test coverage for performing various commands with concurrent collection drops. Can't we just backport the try-catch block so that we handle this in the same way in 2.6 as we do on the more recent branches? |
| Comment by James Wahlin [ 14/Jan/16 ] |
|
david.storch - I propose we remove the queryoptimizer3.js test for 2.6 as it does not appear to be useful either as-is or in its current form on master. I would enter a separate ticket to check for expected assertion codes. Let me know if this sounds reasonable or if you would like to discuss. |
| Comment by James Wahlin [ 14/Jan/16 ] |
|
This test broke because it expects queries killed during a yield to return successfully rather than assert. The 3.0+ version of this test catches these exceptions instead and confirms that the server can still respond to an isMaster call. It allows this test to pass for queries killed during yield, but I am not sure if it is a useful test as |