[SERVER-9673] Intermittent failure during replication unit tests on RHEL 64-bit Created: 13/May/13  Updated: 10/Dec/14  Resolved: 14/May/13

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Eric Milkie
Resolution: Duplicate Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

http://buildlogs.mongodb.org/Nightly%20Linux%20RHEL%2064-bit/builds/516/test/core/test

Mon May 13 02:58:16.872 [testsuite] 	 going to run test: ReplTests::DeleteOpIsIdBased
Mon May 13 02:58:16.873 [testsuite] 	 going to run test: ReplTests::DatabaseIgnorerBasic
Mon May 13 02:58:16.873 [testsuite] 	 going to run test: ReplTests::DatabaseIgnorerUpdate
Mon May 13 02:58:16.873 [testsuite] 	 going to run test: ReplTests::FindingStartCursorStale
Mon May 13 02:58:16.874 [testsuite] 	 going to run test: ReplTests::FindingStartCursorYield
Mon May 13 02:58:16.874 [testsuite] Assertion: 15889:FindingStartCursor::recoverFromYield() failed to recover
Mon May 13 02:58:16.875 [testsuite] 	 going to run test: ReplTests::FindingStartEmptyExtentNonLooped
Mon May 13 02:58:16.876 [testsuite] 	 going to run test: ReplTests::FindingStartTwoEmptyExtentsNonLooped
Mon May 13 02:58:16.877 [testsuite] 	 going to run test: ReplTests::FindingStartTwoEmptyEarlyExtentsNonLooped
Mon May 13 02:58:16.877 [testsuite] 	 going to run test: ReplTests::FindingStartFirstRecordNonLooped
Mon May 13 02:58:16.879 [testsuite] 	 going to run test: ReplTests::FindingStartEmptyExtentLooped
Mon May 13 02:58:16.879 [testsuite] 	 going to run test: ReplTests::FindingStartTwoEmptyExtentsLooped
Mon May 13 02:58:16.880 [testsuite] 	 going to run test: ReplTests::FindingStartTwoEmptyEarlyExtentsLooped
Mon May 13 02:58:16.881 [testsuite] 	 going to run test: ReplTests::FindingStartFirstRecordLooped
Mon May 13 02:58:16.884 [testsuite] 	 going to run test: ReplTests::CapExtentFreshSidePrevExtent
Mon May 13 02:58:16.885 [testsuite] 	 going to run test: ReplTests::CapExtentStaleSidePrevExtent
Mon May 13 02:58:16.887 [testsuite] 	 going to run test: ReplTests::FindingStartSingleExtentNonLooped
Mon May 13 02:58:16.887 [testsuite] 	 going to run test: ReplTests::FindingStartSingleExtentLooped
Mon May 13 02:58:16.889 [testsuite] 	 going to run test: ReplTests::ReplSetMemberCfgEquality
Mon May 13 02:58:16.889 [testsuite] 	 going to run test: ReplTests::ShouldRetry
Mon May 13 02:58:16.889 [testsuite] repl: couldn't connect to server localhost:123
Mon May 13 02:58:16.889 [testsuite] warning: network problem detected while connecting to the sync source, attempt 1 of 3
2013-05-13 02:58:20 EDT	
Mon May 13 02:58:20.891 [testsuite] repl: couldn't connect to server localhost:123
Mon May 13 02:58:20.891 [testsuite] warning: network problem detected while connecting to the sync source, attempt 2 of 3
2013-05-13 02:58:29 EDT	
Mon May 13 02:58:29.894 [testsuite] repl: couldn't connect to server localhost:123
Mon May 13 02:58:29.894 [testsuite] warning: network problem detected while connecting to the sync source, attempt 3 of 3
Mon May 13 02:58:29.894 [testsuite] Assertion: 15916:Can no longer connect to initial sync source: localhost:123
0x1935e21 0x18f8deb 0x18f932c 0x1747cf8 0x10cf6f5 0x10d0370 0x18f4de9 0x18f5d34 0x1769c41 0xa22b5c 0xa22c39 0x30db41d994 0x8bdb89 
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_ZN5mongo15printStackTraceERSo+0x21) [0x1935e21]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_ZN5mongo11msgassertedEiPKc+0x9b) [0x18f8deb]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test [0x18f932c]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_ZN5mongo4Sync13getMissingDocERKNS_7BSONObjE+0x428) [0x1747cf8]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_ZN9ReplTests11ShouldRetry3runEv+0x765) [0x10cf6f5]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_ZN5mongo8unittest5Suite13runTestObjectIN9ReplTests11ShouldRetryEEEvv+0xa0) [0x10d0370]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_ZN5mongo8unittest5Suite3runERKSsi+0x3d9) [0x18f4de9]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_ZN5mongo8unittest5Suite3runERKSt6vectorISsSaISsEERKSsi+0x474) [0x18f5d34]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_ZN5mongo7dbtests10runDbTestsEiPPcSs+0x1621) [0x1769c41]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(_Z11dbtestsMainiPPcS0_+0x6c) [0xa22b5c]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test(main+0x9) [0xa22c39]
 /lib64/libc.so.6(__libc_start_main+0xf4) [0x30db41d994]
 /data/buildslaves/Linux_RHEL_64bit_Nightly/mongo/test [0x8bdb89]



 Comments   
Comment by Eric Milkie [ 14/May/13 ]

The snippit you posted is actually supposed to happen – the same output appears in a passing test.

The failure here appears to be the problem that I fixed for SERVER-8536:
9c046fbf99aada223f2d4d26e331cff0eddc0b98

Generated at Thu Feb 08 03:21:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.