[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: SERVER-9411 SERVER-9678 Fix windows failure.

This change just reduces the number of open files by doubling the memory
limit for the failing test. The long-term solution will be to call
_setmaxstdio(2048) at startup on windows.
Branch: master
https://github.com/mongodb/mongo/commit/763c40a81f19c6cd29dfe9c45251abf69e361223

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