Bug summary
______________________
Summary for 2007-05-27 through 2007-06-03
Bugs opened: 9 Bugs closed: 0 Total open bugs: 969 (+9)
|== Type Changes |== Priority Changes |== Component Changes
|Defect: +7 |Highest: +2 |Conch: +2
|Enhancement: +3 |High: +2 |Core: +4
|Normal: +6 |Mail: +2
|Web: +2
New / Reopened Bugs
______________________
===== Highest =====
[#2682] twisted.conch.ssh.userauth is poorly tested. (opened by z3p)
defect conch http://twistedmatrix.com/trac/ticket/2682
[#2685] factor secure random implementation (opened by antoine)
enhancement core http://twistedmatrix.com/trac/ticket/2685
===== High =====
[#1105] IMAP Client does not seem to handle unsolicited server responses (opened by cablehead)
defect mail http://twistedmatrix.com/trac/ticket/1105
===== Normal =====
[#2680] abdapi ConnectionPool doesn't allow for synchronous close (opened by jml)
defect core http://twistedmatrix.com/trac/ticket/2680
[#2681] twisted.web.distrib non-functional (opened by exarkun)
defect web http://twistedmatrix.com/trac/ticket/2681
[#2683] twisted/web/http.py has self._header instead of self.__header (opened by jvtm)
defect web http://twistedmatrix.com/trac/ticket/2683
[#2684] t.p.t.ThreadPool.dispatch should be deprecated (opened by indigo)
enhancement core http://twistedmatrix.com/trac/ticket/2684
[#2686] AMP implementation: elisp (opened by glyph)
enhancement core http://twistedmatrix.com/trac/ticket/2686
[#2687] Conch blows up when processes end due to signals (opened by jml)
defect conch http://twistedmatrix.com/trac/ticket/2687
Closed Bugs
______________________
Hello,
For my Summer of Code project, I am implementing a distributed trial
test runner (http://code.google.com/soc/psf/appinfo.html?csaid=770D0FCD95DAFF9E).
The following is basically what needs to be done to get distributed
trial working, given a master machine and slaves:
1. Transfer the relevant code to all slave machines. (with conch)
2. Do test loading at least on the master (possibly on each of the
slaves as well)
3. Find a good test-to-unique-id mapping (probably using FQPNs +
something else for test_suite-generated tests?)
4. Implement a visitor which will run through the tests on the master
and split them among the slaves.
5. Figure out how to get SSH command shells open to the slaves and get
individual tests to run
6. Gather results from slaves and give them to a reporter.
I think that is all. Any thoughts? Comments?
Thanks,
Alex
