aaa_profiling/test_pool on py 2.6.5/2.7: "Function call count 59 not within 5.0% of expected 64."

[Former user]

One of the unit tests is failing. To reproduce, unpack the sources on a Solaris 9 SPARC and run the unit tests. The full log is attached; here's a small snippet with the error message:

======================================================================
FAIL: test.aaa_profiling.test_pool.QueuePoolTest.test_first_connect
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/maciej/src/opencsw/pkg/sqlalchemy/trunk/work/solaris9-i386/build-isa-i386/SQLAlchemy-0.6.1/nose-0.11.3-py2.6.egg/nose/case.py", line 186, in runTest
    self.test(*self.arg)
  File "/home/maciej/src/opencsw/pkg/sqlalchemy/trunk/work/solaris9-i386/build-isa-i386/SQLAlchemy-0.6.1/lib/sqlalchemy/test/profiling.py", line 134, in counted
    calls, (variance * 100), count, py_version))
AssertionError: Function call count 59 not within 5.0% of expected 64. (Python version 2.6.5.final.0)
-------------------- >> begin captured stdout << ---------------------
Sun Jun 27 01:32:36 2010    test_first_connect.prof

         59 function calls in 0.000 CPU seconds

[Former user]

Unit test log file

[Mike Bayer]

what python version is it ?

[Former user]

Python 2.6.5, here's the full signature:

> python
Python 2.6.5 (r265:79063, Apr 19 2010, 12:01:34) [C](C) on sunos5
Type "help", "copyright", "credits" or "license" for more information.
>>>

[Former user]

To make issue reproducing easier, OpenCSW offers access to the buildfarm, where you can check out the build description from subversion, and then type "gmake package" to reproduce the issue. You can ask on #opencsw on Freenode, or contact via a mailing list. For more information, you can see: http://www.opencsw.org/extend-it/signup/to-upstream-maintainers/

[Mike Bayer]

this actually reproduces on any 2.6.5 or 2.7 release and the threshold has been upped to 10%.

[Mike Bayer]

Removing milestone: 0.6.2 (automated comment)