test_max_processes is not idempotent

[Jay Pipes]

About once every five times I run:

$ python run_tests.py

I get a test failure on the test_max_processes test case:

===============================================================================
[FAIL]: nova.tests.process_unittest.ProcessTestCase.test_max_processes

Traceback (most recent call last):
Failure: twisted.trial.unittest.FailTest: [Failure instance: Traceback: <class 'twisted.trial.unittest.FailTest'>: not equal:
a = 'd4'
b = 'd3'

/usr/lib/python2.6/dist-packages/twisted/internet/defer.py:354:_startRunCallbacks
/usr/lib/python2.6/dist-packages/twisted/internet/defer.py:371:_runCallbacks
/usr/lib/python2.6/dist-packages/twisted/internet/defer.py:330:_continue
/usr/lib/python2.6/dist-packages/twisted/internet/defer.py:325:unpause
--- <exception caught here> ---
/usr/lib/python2.6/dist-packages/twisted/internet/defer.py:371:_runCallbacks
/home/jpipes/repos/nova/testing-refactor/nova/tests/process_unittest.py:88:<lambda>
/usr/lib/python2.6/dist-packages/twisted/trial/unittest.py:287:failUnlessEqual
]

I can't tell what might be causing this, but if I execute run_tests.py repeatedly, this happens about 1 in 5 times...

[Glyph Lefkowitz (glyph)]

This looks like a test named test_max_processes, not test_too_many_processes.

[Jay Pipes (jaypipes)]

Ooops, nice catch. Corrected the title of the bug.

[Jay Pipes (jaypipes)]

Changing this to Won't Fix, as there is likely going to be a major overhaul of the testing suite post-FF