chimera.core.test.test_locks.TestLock.test_autolock fails

[GoogleCodeExporter]

I'm not sure that this is a serious problem, but...

isaac@isaacE1405 ~/workspace/chimera/src/chimera/core $ nosetests -v
tests/test_locks.py
chimera.core.tests.test_locks.TestLock.test_autolock ... FAIL
chimera.core.tests.test_locks.TestLock.test_lock_config ... ok

======================================================================
FAIL: chimera.core.tests.test_locks.TestLock.test_autolock
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/usr/lib64/python2.5/site-packages/nose-0.10.3-py2.5.egg/nose/case.py",
line 182, in runTest
    self.test(*self.arg)
  File
"/home/isaac/workspace/chimera/src/chimera/core/tests/test_locks.py", line
123, in test_autolock
    doTest(m)
  File
"/home/isaac/workspace/chimera/src/chimera/core/tests/test_locks.py", line
118, in doTest
    assert equals_eps(locked_sigma, 2.581, 0.5)
AssertionError: 
-------------------- >> begin captured stdout << ---------------------

[unlocked] - unlocked-0 - 1.000
[ locked ] -   lock-0 - 1.001
[ locked ] -   with-0 - 1.002
[unlocked] - unlocked-1 - 1.003
[ locked ] -   with-1 - 1.004
[unlocked] - unlocked-2 - 1.005
[ locked ] -   with-2 - 1.007
[unlocked] - unlocked-3 - 1.008
[ locked ] -   with-3 - 1.010
[unlocked] - unlocked-4 - 1.011
[ locked ] -   with-4 - 1.013
[ locked ] -   lock-1 - 2.000
[ locked ] -   lock-2 - 3.000
[ locked ] -   lock-3 - 4.001
[ locked ] -   lock-4 - 5.001
unlocked: mean: 1.005551 sigma: 0.004135
locked  : mean: 2.004056 sigma: 1.411802

--------------------- >> end captured stdout << ----------------------

----------------------------------------------------------------------
Ran 2 tests in 6.005s

FAILED (failures=1)
isaac@isaacE1405 ~/workspace/chimera/src/chimera/core $ 

Original issue reported on code.google.com by laughing...@gmail.com on 23 Jul 2008 at 6:50

[GoogleCodeExporter]

Yeah, this is a hard to test feature. The AssertionError was given (probably) 
'cause
of the load on your machine was high (much more than pure idle machine) and the 
test
took too long.

It's certainly not an error per se, but we need to figure out how to implement 
the
test in a load independent way. Leave open just in case.

Original comment by ph.silva on 24 Jul 2008 at 3:28

[GoogleCodeExporter]

Fixed on r268. There was a bug actually introduced on my last 'kill all failing 
test
cases' commit on r263.

Test it and reopen if needed.

Original comment by ph.silva on 24 Jul 2008 at 7:22

• Changed state: Fixed