Hi Meme, On Thu, Apr 22, 2010 at 22:35 +1000, meme dough wrote: > > Just did checkins to py-trunk and xdist implementing a first go at this, > > bumping internal version numbers to 1.2.2 and 1.2 respectively. > > (hudson testruns are ongoing at http://hudson.testrun.org/view/pytest/) > > > >> If you'd like to push ahead before i finish this you can just add the > >> hooks statically and i patch it out later. > > > > It should be easy to add new hooks now to xdist/newhooks.py > > I've pulled in changes and looks good. > > Another commit to xdist for putting slaveinput / slaveoutput on the > config object for slaves. For master remains on the node since many > nodes, this also allows checking if running as slave as you pointed > out. > > I renamed to slaveinput / slaveoutput as had in previous email. > > I also changed the test so that instead of asserts in the hooks on > slave or master it will output something at summary and the test > process can check. > > http://bitbucket.org/memedough/pytest-xdist-slaveready-config/changeset/5257145dbd4b
I pulled it and did another patch to use a new configure-node hook. > An issue though: > > Last execnet commit is 1.0.6 version bump but not tagged or released > on pypi. Hence can't install or develop pytest-xdist. I changed > locally but didn't put in this changeset. Not sure if you want to > down xdist to point 1.0.5 or release execnet 1.0.6. Both - xdist now only requires 1.0.5 but i'd like to put out 1.0.6 soonish. A question - do i guess right that your distributed coverage plugin is to use the new slaveinput/slaveoutput mechanism? cheers, holger > :) > -- _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
