Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Tornado Web Server
Home
+ new post
About this group
Join this group
Message from discussion Timeouts in tests using Tornado + Motor
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Ben Darnell  
View profile  
 More options Oct 4 2012, 11:53 pm
From: Ben Darnell <b...@bendarnell.com>
Date: Thu, 4 Oct 2012 20:53:08 -0700
Local: Thurs, Oct 4 2012 11:53 pm
Subject: Re: [tornado] Timeouts in tests using Tornado + Motor
Print | View thread | Show original | Report this message | Find messages by this author
This sounds like it might be a file descriptor leak.  Your tests might
be opening sockets and not closing them, which would cause problems
once you hit the file descriptor limit, which is relatively low by
default on many platforms.  Try increasing the limit by running "uname
-n 10000" before running your tests (if you're on linux and the OS
won't let you, try increasing the settings in
/etc/security/limits.conf).  If that works, then you're running out of
file descriptors.  Once you've confirmed the problem, a better
long-term solution is to ensure that you're closing all the file
descriptors you're opening.  This includes sockets and regular files,
as well as other file descriptors created by IOLoop and
AsyncHTTPClient (could you be forgetting to call super.tearDown() in
your tests?).

-Ben

On Thu, Oct 4, 2012 at 5:50 PM, Daniel Kador <d...@keen.io> wrote:
> Hi!

> I'm running into (what I perceive to be) a strange problem with my tests.
> I've got an application written on top of Tornado that communicates with
> Mongo through the Motor library.  It's humming away nicely in production
> (daemonized using supervisord).  The only problems (that I can detect) are
> with my tests.  I'm very happy to acknowledge that this could be a problem
> in my application layer, or in the Motor layer, or maybe even in MongoDB
> itself - mostly I'm looking for some guidance as I'm not really sure where
> to start digging in.

> But let me step back and describe what I've noticed in more detail.

> I have approximately ~150 tests that extend the
> tornado.testing.AsyncHTTPTestCase class, spread across a number of my own
> classes.  I have ~50 that are simple unit tests.  They both communicate to
> Mongo through Motor.  The unit tests are fast and never fail (I mention this
> only as a data point that may show Motor by itself may not be the culprit).
> The AsyncHTTPTestCase tests all pass when their various test classes are run
> individually.

> But when I run them all together, after about ~65 tests running and passing,
> I start getting timeouts in various spots.  Sometimes it's when interacting
> directly with Motor.  Sometimes it's when making an async HTTP request to
> one of the APIs I've created (which, under the covers, is talking to Mongo
> through Motor).  But it's always when calling (from a test) self.wait().

> It's getting to be a serious problem, as now I can't actually run all my
> tests locally (at one time).  Obviously not a recipe for test-driven
> development success.

> I'm relatively sure I've done something stupid, but I haven't figured out
> where yet.  Would really appreciate some help here.

> Thanks!

> -Dan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google