[SERVER-12716] removec.js failing in sharding passthrough Created: 13/Feb/14 Updated: 11/Jul/16 Resolved: 15/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
Earliest confirmed failure is https://github.com/mongodb/mongo/commit/228c5a2e27cdaf35e1ac7e0a097d8172f7f4a387 But there's a long stretch of red before it, so it may have begun earlier. Sample output at http://buildlogs.mongodb.org/mci_0.9_linux_64/builds/69321/test/slow_nightly_tests_0/sharding_passthrough.js Relevant output:
|
| Comments |
| Comment by Githook User [ 14/Feb/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'gregs', u'email': u'greg@10gen.com'}Message: |
| Comment by Greg Studer [ 14/Feb/14 ] |
|
Confirmed. |
| Comment by Greg Studer [ 13/Feb/14 ] |
|
Issue to be confirmed by patch above is twofold: 1) It is never sane or valid to check the result of find() via getLastError - though it does appear that internally v8_db.cpp::internalCursorNext() uses DBClientCursor::next() instead of nextSafe(). This would prevent some/all errors from being correctly thrown in the shell and may be why this test is written this way. 2) Every DBException thrown sets the last error value - versioning sometimes handles exceptions which should not be reported but are. Not a regression, but unpredictable and subject to timing issues. Once confirmed, fix should be to the shell and the test. |
| Comment by Githook User [ 13/Feb/14 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@10gen.com'}Message: |