[SERVER-11270] explainb.js failed on OS X 10.8 C++11 DEBUG Created: 18/Oct/13 Updated: 11/Jul/16 Resolved: 04/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matt Kangas | Assignee: | hari.khalsa@10gen.com |
| Resolution: | Done | Votes: | 0 |
| Labels: | build-failure, buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
d908b8726048 OS X 10.8 C++11 DEBUG js (logfile)
|
| Comments |
| Comment by auto [ 04/Nov/13 ] | |||||||||
|
Author: {u'username': u'hkhalsa', u'name': u'Hari Khalsa', u'email': u'hkhalsa@10gen.com'}Message: | |||||||||
| Comment by Ernie Hershey [ 31/Oct/13 ] | |||||||||
|
Verified this is still erroring in recent commit today at 3:39 pm - http://github.com/mongodb/mongo/commit/eab2644c221206c121ac1ab93fcf95c8100f4ff3 | |||||||||
| Comment by Andrew Morrow (Inactive) [ 18/Oct/13 ] | |||||||||
|
I should add that I have the first part of this change done already: if there is an easy explanation/fix for the [2] != [4] error I can take care of that in my tree and get this sent out for review. I would be interested to hear thoughts on this test from hari.khalsa@10gen.com or alerner. If it is an easy fix it would be nice to get this builder back to green. | |||||||||
| Comment by Andrew Morrow (Inactive) [ 18/Oct/13 ] | |||||||||
|
Well, the failure at line 15 seems to be because it is expecting one plan to complete before the other, though I see no reason that that must be true. So I think the fix for line 16 is to either remove the assert, or change it to something like:
A similar fix needs to be made on line 30 or so. What is more interesting is that after making those changes the test still fails:
This is the line
I'm not sure why this value would change: someone more aware of the internals of the new query framework would need to comment on that. | |||||||||
| Comment by Eric Milkie [ 18/Oct/13 ] | |||||||||
|
I showed this to Alberto a couple days ago and he started looking into it a bit. |