[SERVER-10157] access violation during BtreeTests1::MoveBelowLowWaterMarkRight on Windows 32-bit Created: 10/Jul/13  Updated: 10/Dec/14  Resolved: 12/Jul/13

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

Type: Bug Priority: Major - P3
Reporter: Matt Kangas Assignee: hari.khalsa@10gen.com
Resolution: Cannot Reproduce Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

buildbot: Windows 32-bit


Operating System: ALL
Participants:

 Description   

Woah. Hard exit during BtreeTests1 unit test on build #5970. Previous build was green.

Builder Windows 32-bit Build #5970

http://buildbot.mongodb.org/builders/Windows%2032-bit/builds/5970/steps/test_1/logs/stdio
http://buildlogs.mongodb.org/Windows%2032-bit/builds/5970/test/core/test.exe

Wed Jul 10 15:25:28.102 [testsuite] 	 going to run test: class BtreeTests1::MoveBelowLowWaterMarkRight
Wed Jul 10 15:25:28.149 [testsuite] *** unhandled exception (access violation) at 0x00FD9C52, terminating
Wed Jul 10 15:25:28.149 [testsuite] *** access violation was a write to 0x092BC017
Wed Jul 10 15:25:28.149 [testsuite] *** stack trace for unhandled exception:
Wed Jul 10 15:25:28.929 [testsuite] test.exe      ...\src\mongo\db\btree.h(242)                       mongo::DiskLoc56Bit::operator=+0x32
Wed Jul 10 15:25:28.929 [testsuite] test.exe      ...\src\mongo\dbtests\btreetests.inl(866)           BtreeTests1::MergeSizeBase::run+0x1c4
Wed Jul 10 15:25:28.929 [testsuite] test.exe      ...\src\mongo\unittest\unittest.h(297)              mongo::unittest::Suite::runTestObject<BtreeTests1::MoveBelowLowWaterMarkRight>+0x5d
Wed Jul 10 15:25:28.929 [testsuite] test.exe      ...\src\mongo\unittest\unittest.cpp(164)            mongo::unittest::Suite::run+0x5d2
Wed Jul 10 15:25:28.929 [testsuite] test.exe      ...\src\mongo\unittest\unittest.cpp(228)            mongo::unittest::Suite::run+0x4fd
Wed Jul 10 15:25:28.929 [testsuite] test.exe      ...\src\mongo\dbtests\framework.cpp(260)            mongo::dbtests::runDbTests+0x11ae
Wed Jul 10 15:25:28.929 [testsuite] test.exe      ...\src\mongo\dbtests\dbtests.cpp(40)               dbtestsMain+0x114
Wed Jul 10 15:25:28.929 [testsuite] test.exe      ...\src\mongo\dbtests\dbtests.cpp(51)               wmain+0x4f
Wed Jul 10 15:25:28.929 [testsuite] test.exe      f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c(278)  __tmainCRTStartup+0x10b
Wed Jul 10 15:25:28.929 [testsuite] kernel32.dll                                                      BaseThreadInitThunk+0x12
Wed Jul 10 15:25:28.929 [testsuite] ntdll.dll                                                         RtlInitializeExceptionChain+0x63
Wed Jul 10 15:25:28.929 [testsuite] 
Wed Jul 10 15:25:28.944 [testsuite] writing minidump diagnostic file mongo.dmp
Wed Jul 10 15:25:29.584 [testsuite] *** immediate exit due to unhandled exception

Could this be related to Andy's logging system rodeo? I don't see it implicated in the stack trace.



 Comments   
Comment by Eric Milkie [ 10/Jul/13 ]

matt.kangas@10gen.com actually the previous build was fake-green, in that it lied about doing any build. You can tell if a green build is fake by looking to see if all the phases completed in "0 seconds". Only the Windows 32-bit builder has this problem, and to fix it you can click on Graceful Shutdown (we've set it up to restart automatically).

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