[SERVER-9777] sharding/sort1.js is timing out in enterprise builds Created: 24/May/13  Updated: 10/Dec/14  Resolved: 24/May/13

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Ernie Hershey
Resolution: Duplicate Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Started happening since 24 hours ago.

http://buildlogs.mongodb.org/Nightly%20Linux%2064-bit%20C%2B%2B11%20Subscription%20Ubuntu%201204/builds/104/test/sharding/sort1.js

http://buildlogs.mongodb.org/Nightly%20OS%20X%2064-bit%2010.7%20C%2B%2B11%20DEBUG%20Subscription/builds/96/test/sharding/sort1.js

http://buildlogs.mongodb.org/Nightly%20Linux%2064-bit%20Subscription%20RHEL%205.7/builds/403/test/sharding/sort1.js

http://buildlogs.mongodb.org/Nightly%20Linux%2064-bit%20Subscription%20Ubuntu%201204/builds/98/test/sharding/sort1.js



 Comments   
Comment by Eric Milkie [ 24/May/13 ]

fixed in buildbot-255

Comment by Eric Milkie [ 24/May/13 ]

Note that because of auth, the sort1.js test takes 20 minutes instead of 1 minute to run, and is no longer testing anything useful due to this (it's supposed to be a relative timing test).

Comment by Eric Milkie [ 24/May/13 ]

Turns out this was due to BUILDBOT-255

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