[SERVER-7863] drop2.js failing on OS X DEBUG build Created: 06/Dec/12  Updated: 11/Jul/16  Resolved: 14/Dec/12

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

Type: Bug Priority: Critical - P2
Reporter: Ian Whalen (Inactive) Assignee: Randall Hunt
Resolution: Done 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/OS%20X%2010.5%2064-bit%20DEBUG/builds/1672/test/recent%20failures/sharding_passthrough.js



 Comments   
Comment by Randall Hunt [ 10/Dec/12 ]

I already set the ulimit to 2048 on all of the mac builders – I just bumped this one to 4096.

bs-mm2:~ yellow$ sudo launchctl limit
	cpu         unlimited      unlimited      
	filesize    unlimited      unlimited      
	data        unlimited      unlimited      
	stack       8388608        67104768       
	core        0              unlimited      
	rss         unlimited      unlimited      
	memlock     unlimited      unlimited      
	maxproc     2048           2048           
	maxfiles    4096           4096

There could be an issue where the buildslave doesn't adopt new limits until the process is restarted or the machine is restarted? I'll try that now.

Comment by Eliot Horowitz (Inactive) [ 10/Dec/12 ]

ulimit is too low, can you raise to 1024?
on all mac builders if possible

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