[SERVER-9678] extsorttest failures on Windows Created: 14/May/13 Updated: 11/Jul/16 Resolved: 15/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Windows |
| Steps To Reproduce: | http://buildbot.mongodb.org/builders/Windows%2064-bit%202008R2%2B/builds/31/steps/test_1/logs/stdio |
| Participants: |
| Description |
|
Assertion: 16818:error opening file "/tmp/unittest/_tmp/extsort.2047": errno:0 The operation completed successfully. It seems that Windows does not set a LastError state when a streams operation fails (or rather, I can't figure out how you're supposed to fetch it, if not with GetLastError()). This is unlike Linux which sets errno when a streams operation fails. |
| Comments |
| Comment by auto [ 14/May/13 ] |
|
Author: {u'date': u'2013-05-14T17:22:43Z', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This change just reduces the number of open files by doubling the memory |