On 04/29/2012 11:28 AM, Daniel Nichter wrote:
Patrick,
I've started learning kewpie but I've had to figure it out by trial and error.
Ultimately I found that this works:
tests$ ./kewpie/kewpie.py --suite
/Users/daniel/dev/drizzle/trunk/plugin/slave/tests/ --mode dtr --testdir=$PWD
All those options are required, else kewpie doesn't find tests. Is this
command line normal?
Still working on this one - next week.
Also, there seems to be no documentation for how to setup a slave or what the
conventions are.
slave/tests/t/master.cnf seems to create a slave, which is confusing
given that the file is called "master.cnf".
So, this is a bit of a break from MTR, but I really, really hated how
each server you wanted to use for a test required a separate *.cnf file.
I'm open to suggestions for other names, but I personally prefer the
idea of a single .cnf file that defines everything that is happening in
the test.
servers = [[--innodb.replication-log],[--plugin-add=slave
--slave.config-file=$MASTER_SERVER_SLAVE_CONFIG]]
Also, that file uses $MASTER_SERVER_SLAVE_CONFIG which isn't documented.
Ok, so I have kewpie create a slave config file for each server that is
started (this may change, but it seemed to make sense at the time). The
file contains what should be needed for a slave server to replicate from
the associated server. This allows us to just point prospective slaves
at the file and have replication running.
Please document for us how to use kewpie to test Drizzle plugins? :-)
Thanks!
-Daniel
_______________________________________________
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
