++ to this. If one was feeling *really* ambitious (and crazy and
slightly drunk), then one could tinker with the randgen and create a new
Executor module, but this is not a trivial task ; )
However, this did seem worth mentioning...should anyone feel like doing
battle with perl, I'd be happy to discuss this path further.
imho, the shell script path is the quickest / easiest to get up and running.
patrick
On 07/10/2012 03:12 PM, Henrik Ingo wrote:
Ah yes. If we could write a shell script that forks several
subprocesses that issue http requests in parallel, then this could be
a useful test. The script could simply be a part of the test/
directory.
henrik
On Tue, Jul 10, 2012 at 8:25 PM, pcrews <glee...@gmail.com> wrote:
On 07/10/2012 05:28 AM, Mohit Srivastava wrote:
Hi,
Recently I have added multithreading feature in json server.
Please elaborate the way to test multithreading feature.
Thanks
--
Mohit
Hi Mohit,
I'll have to ponder this for a bit. Probably the quickest way would be to
use kewpie + python unittests, but we currently aren't executing such tests
in jenkins (yet).
It might be possible to do this with regular drizzle-test-run test cases (as
you have been using until now), but you would need some script that would
generate the multiple json requests / + execute them.
Do you have a branch you could link to so I can check things out?
Thanks,
Patrick
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : drizzle-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : drizzle-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
