multiprocessing plugin fails with custom plugins

nose-devs / nose

nose is nicer testing for python

http://readthedocs.org/docs/nose/en/latest/

1.36k stars 395 forks source link

multiprocessing plugin fails with custom plugins #702

Open pdox opened 11 years ago

pdox commented 11 years ago

The multiprocess plugin passes the "config" object to subprocesses as a pickled string. (see nose.plugins.multiprocess.MultiProcessTestRunner.startProcess).

This conversion process will fail silently if the config contains custom plugin classes which cannot be re-imported/re-initialized by pickle.

Removing the pickle loads/dumps fixes this problem. (it is not clear to me why the config is pickled in the first place, since each process will get its own copy anyway)

talbenbasat commented 10 years ago

Me and my team have encountered the same problem. We used nose with our own built in plugin and adding multiprocessing plugin disabled it operation.

Further Exploring

As for the 24/08/2014 there were no pull requests, forks or other issues regarding this issue.
When you build a plugin and register it with an entry point, using pip or easy_install, the custom plugins works.