[TIP] Fwd: Bizarre results running Hudson job + CI

Jesse Noller jnoller at gmail.com
Mon Mar 22 09:45:28 PDT 2010

>> The version of python they have installed does not have
>> multiprocessing compiled into it. Without knowing the underlying
>> platform, and seeing the output from make when running the compile,
>> it's impossible to tell why.
> Jesse's leaping to conclusions but they're justified -- Olemis, you need
> to check to see what the tests respond with when you run them on that
> machine by hand.  Right now you can't tell if it's a Hudson problem (probably
> path-related) or a Python installation problem.
> cheers,
> --titus

I'd say they're justified:

 'Internal Server Error\n\nTracError: ImportError: No module named

Is a dead giveaway. That's the error thrown when multiprocessing is
missing from core.

More information about the testing-in-python mailing list