> I'm wondering if we might have a problem where two daemons can be started > to run a build under certain circumstances. I don't have another > explanation for the failure, other than the test fixture being bugged. >
There might be a bug so that we start a daemon but for whatever reason it didn't except the build request (for example: issue with remoting, daemon says I'm busy, etc.). So the implementation starts a new daemon and try to pass him the build request. I've seen this issue with this test before. This symptom can also be caused by our daemon test harness. To fix this we need to refactor the test so that it's easier to debug and more reliable. We talked about it before - I have some plan for it and I'm hoping I'll have time to do it at some point. If someone works on it, let me know ;). Hope that helps! > > -- > Luke Daley > Principal Engineer, Gradleware > http://gradleware.com > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- > Szczepan Faber > Principal engineer@gradleware > Lead@mockito > > <http://xircles.codehaus.org/manage_email>
