I created two more tests for Rodrigo’s auto-start command line parsing code. The first one which spawns a service over the bus and has it send its arguments in the reply works flawlessly so I was about to say it is ready to be checked into CVS.

That was until I created a second test that spawned a service with faulty quoting on the command line. This should produce an invalid argument error over the bus but instead I get a timeout. This is not an error in Rodrigo’s code as far as I can tell but a bug in dbus that seems to not want to propigate this error. I can confirm that it issues the command to send it but it never gets into the test suites queue and instead we timeout waiting for a reply. Unfortunatly until I figure this out I can’t check the code in.

I’m running the testsuite with DBUS_VERBOSE=1 which even with just the one test enabled produced 317M of debug spew. I need to figure out a way to turn off the out of memory tests so I can debug what is going wrong a bit quicker.

UPDATE:

It actually succeeds once and then timesout on the last call. Is this another manifestation of the old activation bug that was fixed recently?

[read this post in: ar de es fr it ja ko pt ru zh-CN ]