Hi, Invoke distributed testing with 2 test process both of which are on the same host but have different dirs:
py.test --dist=each --tx=popen//chdir=/tmp/testarea1//python=/usr/bin/python2.5 --tx=popen//chdir=/tmp/testarea2//python=/usr/bin/python2.6 --rsyncdir=circuits The 2 test process are started by popen, and each one changes to it's respective dir. The /tmp/testarea1 & 2 get created. The circuits dir should be rsynced to the test areas. py.test will automatically send what it needs to work (py and xdist packages). Then you can see what happens in each test area. Look at what it rsyncs, does it send over the pyc files? Since each is separate then any generation of new pyc files should not conflict between the processes. This works for me but I'm not getting the same errors as you. :) On 9 July 2010 18:55, James Mills <prolo...@shortcircuit.net.au> wrote: > On Fri, Jul 9, 2010 at 6:39 PM, meme dough <memedo...@gmail.com> wrote: >> Did you try deleting all .pyc and .pyo files in >> /home/prologic/work/circuits recursively and then trying? > > Yes, tried and same result. > >> Since it looks like python 2.6 will create the pyc files in the master >> process and then the popen to python 2.5 barfs on them. As Holger >> pointed out PYTHONDOWNWRITEBYTECODE should turn off the master python >> 2.6 creating pyc files. But if you've still got old ones lying around >> then the slave python 2.5 will no doubt barf. > > Also tried, same result. > >> Another solution to this maybe to give each test process it's own >> area. So change the working dir of each tx and specify the rsync >> option to get the proper code to each test area (I assume the rsync >> doesn't push pyc files). Also that way if your code relies on it's >> own resources in the dir tree (writing out to a log file for example) >> then they will be separate and not clash. > > Could you show an example tx config that does thsi ? > > cheers > James > > -- > -- James Mills > -- > -- "Problems are solved by method" > _______________________________________________ > py-dev mailing list > py-dev@codespeak.net > http://codespeak.net/mailman/listinfo/py-dev > _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
