[SERVER-7878] repl_monitor_stress.js timing out Created: 07/Dec/12 Updated: 15/Feb/13 Resolved: 07/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Randolph Tan |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Interestingly it passes when run as a "recently failed test" but fails when run as part of the larger suite: http://buildbot.mongodb.org/builders/Nightly%20Linux%20RHEL%2064-bit/builds/318/steps/test/logs/stdio |
| Comments |
| Comment by Randolph Tan [ 07/Dec/12 ] |
|
This is timing related -> the test passes or fails depending on how long it took the replica set to elect the new primary. This is not even part of what this file is meant to test, but is just part of setting the test up. Now that the MockReplicaSet is available, I am converting this into a cpp test that would eliminate all of these timing issues and should run a magnitude faster than the current one. |