[SERVER-5206] isMaster.localTime asserting in dbadmin.js Created: 05/Mar/12 Updated: 11/Jul/16 Resolved: 05/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Nightly Linux 64-bit Legacy |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
| Comments |
| Comment by auto [ 03/Apr/12 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |
| Comment by Ian Whalen (Inactive) [ 29/Mar/12 ] |
|
http://buildbot.mongodb.org/builders/Linux%2064-bit/builds/4304/steps/test_6/logs/stdio |
| Comment by siddharth.singh@10gen.com [ 07/Mar/12 ] |
|
The test compares the current system time against what is returned by isMaster command and asserts if the difference is less than 5 milliseconds. The build machine might have slowed down during these two operations and the difference was 29 mill and hence the test failed. This is intermittent and shouldn't happen very often. If we see a lot of builds breaking cause of this we can later choose to increase the 5 millisecond number to a higher value. |