Oliver Falk oliver@linux-kernel.at writes:
Am 2007-02-25 21:26, Ken MacLeod schrieb: [ ... ]
Here's what I've done so far:
- common/XMLRPCServerProxy.py
- set self._use_datetime = 0
Why that?
- common/AuthedXMLRPCServer.py
SimpleXMLRPCServer.SimpleXMLRPCDispatcher's
- pass allow_none=False and encoding=None to
Why that?
Yes, as Dan mentioned, both due to Python 2.5.
So you' running 0.5.0 now. The same as I do. Right?
It's more accurate to say I'm running CVS MAIN, but yes ;-)
Example config: builder.cfg: ==================================== [General] comm_type = active
[Active] xmlrpc_port = 8889 fileserver_port= 8890
server.cfg:
[Active Builders] xmlrpc_server_port = 8889 file_server_port = 8890
[UI]
port = 8887
If you need help creating the ssl certificates or anything else, just mail me. :-) And don't use sqlite as database backend; It often runs into locking problems; That's why I switched to mysql.
The above config (thanks!) and switching to MySQL has got the builder and server talking to each other and queueing jobs. Not that this changes anything, but I also backed out the sqlite changes that I can't verify. So I still have the XMLRPC change I made and DBManager change same as yours.
I don't remember if I created /tmp/builder_work or if the server or builder created it, but on the job I just queued the builder gets an error because /tmp/builder_work is owned by root and the builder can't get access to it.
I killed the job (noted a typo in the message about not being able to send mail, patch sent) and requeued. A couple minor glitches later...
Success!
However, you do need to create the tables in the mysql database first. I have the statements ready if you need...
I didn't see that, the tables got created.
Going to test it out some more...
-- Ken