Hi everyone, Just wanted to provide an update on DBT2 and Drizzleslap.
We had been seeing a lot of failures for these tests and I now believe they have been sorted out. Both of these tests were failing early on (initial server startup / pre-test-data loading) For DBT2, it was that we weren't specifying a secure-file-priv value so we could load the DBT2 data (Thanks to Lee for helping to point me in the right direction here). It has been tested and works fine now. The config file now includes the secure-file-priv option and this has been pushed to trunk. For Drizzleslap, I will admit that I am not 100% certain what fixed this. As randgen used a similar process for starting / setting up the servers, I included some calls that randgen/run.py used that weren't in drizzleslap/run.py (mostly with setting up startup options for the server). I don't believe this fixed things, but it could be possible that I tested too quickly. The last thing I did was to add a call to server.ping() after the initial server.start(). >From looking at the code in server/drizzled.py, it seems that we start the server and wait a given amount of time, but we don't really fail the test if the server hasn't started by the end of the timeout. I added the call to ping() to make sure the server is really running before proceeding. It could be possible that the server was a bit slow to start up or my addition of the code from randgen fixed things. I'm not sure. In any case, drizzleslap is currently running, but we'll need to keep an eye on things for a bit to make sure that it works consistently. Thanks, Patrick
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-builds Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-builds More help : https://help.launchpad.net/ListHelp
