[SERVER-5141] cloneDb.js failing on Windows 32-bit build Created: 29/Feb/12 Updated: 25/Jul/13 Resolved: 29/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Whalen (Inactive) | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | buildbot | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 32-bit |
||
| Operating System: | Windows |
| Participants: |
| Description |
|
http://buildbot.mongodb.org/builders/Windows%2032-bit/builds/4647/steps/test_2/logs/stdio |
| Comments |
| Comment by Tad Marshall [ 01/Mar/12 ] |
|
I left cloneDb.js running in a loop from a batch file against the 32-bit Windows build after adding the imnproved unhandled exception handler so I would see the crash address if it crashed. It was still running the next morning after completing the test 472 times, so it doesn't look reproducible on my machine. |
| Comment by Tad Marshall [ 29/Feb/12 ] |
|
Could not reproduce it locally and BuildBot ran it successfully on the next pass, so I'm not sure what the issue is. The exception handler we have set up on Windows is not very helpful ... it prints "access violation" with no address or stack trace so there is no trail to follow. |
| Comment by Tad Marshall [ 29/Feb/12 ] |
|
We get an "unhandled windows exception", seemingly in the shell (from my attempt at interpreting the log) and I'm doing a local build to try to reproduce it in the debugger. |