[Twisted-Python] Make Twisted/PyPy a milestone?
Hi all, I'd like to ask if it would be appropriate and whether there is interest in making "support Twisted on PyPy" a project milestone for Twisted. I'd start contributing by setting up a buildslave for PyPy so that issues can be made transparent and identified and progress tracked. Since PyPy is still very fast moving, that would need to be a beefy machine, since I would track PyPy trunk doing nightly PyPy builds and then use that for Twisted trials. It likely would involve stopping buildbot for the short period of PyPy installation, restarting it afterwards. Is there community interest in Twisted/PyPy .. people that might help with working on tickets (which I guess will likely result from such an effort)? My hope would also be that PyPy devs might be interested in having the PyPy codebase tested against such a broad suite like Twisted on a regular basis and would help with PyPy non-Twisted-but-triggered issues .. Cheers, Tobias PS: The current trial results (Ubuntu 10.04 LTS i386, Twisted trunk, select reactor) twisted.conch.test.test_manhole => ManholeLoopbackStdio: timeouts on all 13 test cases twisted.conch.test.test_recvline => HistoricRecvlineLoopbackStdio: timeouts on all 2 test cases => RecvlineLoopbackStdio: timeouts on all 9 test cases twisted.internet.test.test_endpoints => ServerStringTests => test_ssl: hangs forever!
Tobias Oberstein
Hi all,
I'd like to ask if it would be appropriate and whether there is interest in making
"support Twisted on PyPy"
a project milestone for Twisted.
To a large extent, it is already supported (although not everything works yet. It has been deployed in production though (twistedmatrix.com is largely hosted on pypy+twisted).
I'd start contributing by setting up a buildslave for PyPy so that issues can be made transparent and identified and progress tracked.
Since PyPy is still very fast moving, that would need to be a beefy machine, since I would track PyPy trunk doing nightly PyPy builds and then use that for Twisted trials. It likely would involve stopping buildbot for the short period of PyPy installation, restarting it afterwards.
That would be useful. We currently do have a buildslave running tests against pypy, but we are looking at decomissioning it. The buildbot takes care of installing new versions of pypy (on a weekly basis). I'll need the follwing information from you (offlist): 1. Desired slave name. This will show up on http://buildbot.twistedmatrix.com/buildslaves 2. Password This is sent cleartext. 3. Email address This is used to send mail messages when the slave disappears. It isn't visible. 5. How many parallel builds you want allowed to run.
PS: The current trial results (Ubuntu 10.04 LTS i386, Twisted trunk, select reactor) ...
You should open tickets for these issues.
On 23 Jun, 01:02 pm, tobias.oberstein@tavendo.de wrote:
Hi all,
I'd like to ask if it would be appropriate and whether there is interest in making
"support Twisted on PyPy"
a project milestone for Twisted.
I'd start contributing by setting up a buildslave for PyPy so that issues can be made transparent and identified and progress tracked.
Of course, feel free to contribute more reliable slaves to the project. But there is already a PyPy builder set up, and has been for several years. A more productive contribution would probably be to fix the tests that have been failing on it for most or all of that time. :)
Since PyPy is still very fast moving, that would need to be a beefy machine, since I would track PyPy trunk doing nightly PyPy builds and then use that for Twisted trials. It likely would involve stopping buildbot for the short period of PyPy installation, restarting it afterwards.
Fortunately this isn't required. Jean-Paul
Is there community interest in Twisted/PyPy .. people that might help with working on tickets (which I guess will likely result from such an effort)?
My hope would also be that PyPy devs might be interested in having the PyPy codebase tested against such a broad suite like Twisted on a regular basis and would help with PyPy non-Twisted-but-triggered issues ..
Cheers, Tobias
PS: The current trial results (Ubuntu 10.04 LTS i386, Twisted trunk, select reactor)
twisted.conch.test.test_manhole
=> ManholeLoopbackStdio: timeouts on all 13 test cases
twisted.conch.test.test_recvline
=> HistoricRecvlineLoopbackStdio: timeouts on all 2 test cases
=> RecvlineLoopbackStdio: timeouts on all 9 test cases
twisted.internet.test.test_endpoints
=> ServerStringTests => test_ssl: hangs forever!
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
more productive contribution would probably be to fix the tests that have been failing on it for most or all of that time. :)
Ok. I guess for that filing tickets first might be the way to go. Hence, I created a "meta bug" http://twistedmatrix.com/trac/ticket/5735 to group the current issues FAILED (skips=1665, expectedFailures=11, failures=11, errors=19, successes=6412) and determine if they are Twisted or PyPy business. Then I go and fix what I can do .. For the initial screening (in particular), any eyes/knowledge/guidance is appreciated ..
participants (3)
-
exarkun＠twistedmatrix.com -
Tobias Oberstein -
Tom Prince