[SERVER-18201] disk/repair5.js fails intermittently Created: 24/Apr/15 Updated: 19/Sep/15 Resolved: 28/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.2 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Kaloian Manassiev |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
54c25da33e Windows 64-bit disk
|
| Comments |
| Comment by Githook User [ 24/Apr/15 ] | ||||||||||||||||||||||||||||
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: | ||||||||||||||||||||||||||||
| Comment by Githook User [ 24/Apr/15 ] | ||||||||||||||||||||||||||||
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: This fails the test, because it is declared to 'use strict' | ||||||||||||||||||||||||||||
| Comment by Githook User [ 24/Apr/15 ] | ||||||||||||||||||||||||||||
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: While at it, I also put the test into a function so it doesn't change | ||||||||||||||||||||||||||||
| Comment by Kaloian Manassiev [ 24/Apr/15 ] | ||||||||||||||||||||||||||||
|
Looks like this is related to commit 8b7528029686ca1ae0eec681169406d52eb27682, which is causing the test shell to go against the wrong mongod instance. | ||||||||||||||||||||||||||||
| Comment by Spencer Brody (Inactive) [ 24/Apr/15 ] | ||||||||||||||||||||||||||||
|
Both this and BF-872 involve waiting for something to show up in currentOp() and not finding it. I suspect they may have the same root cause, something to do with currentOp(). | ||||||||||||||||||||||||||||
| Comment by Spencer Brody (Inactive) [ 24/Apr/15 ] | ||||||||||||||||||||||||||||
|
Huh, almost looks like the command may be returning success before actually doing its work?
though you can't really trust the order of log messages displayed across processes in buildlogger, so may also be a red herring. |