-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ntwrkd wrote: > I am running the --start-and-exit test and I'm not getting any result. > Is this expected behaviour? > > [driz...@fedoradev tests]$ ./dtr --start-and-exit > Logging: ./dtr --start-and-exit > InnoDB: The first specified data file ./ibdata1 did not exist: > InnoDB: a new database to be created! > 090308 14:35:33 InnoDB: Setting file ./ibdata1 size to 10 MB > InnoDB: Database physically writes the file full: wait... > 090308 14:35:34 InnoDB: Log file ./ib_logfile0 did not exist: new to be > created > InnoDB: Setting log file ./ib_logfile0 size to 5 MB > InnoDB: Database physically writes the file full: wait... > 090308 14:35:34 InnoDB: Log file ./ib_logfile1 did not exist: new to be > created > InnoDB: Setting log file ./ib_logfile1 size to 5 MB > InnoDB: Database physically writes the file full: wait... > InnoDB: Doublewrite buffer not found: creating new > InnoDB: Doublewrite buffer created > InnoDB: Creating foreign key constraint system tables > InnoDB: Foreign key constraint system tables created > 090308 14:35:34 InnoDB Plugin 1.0.2 started; log sequence number 0 > 090308 14:35:34 InnoDB: Starting shutdown... > 090308 14:35:35 InnoDB: Shutdown completed; log sequence number 46409 > Plugin 'MyISAM' has ref_count=1 after deinitialization.MySQL Version 7.0.0 > Using MTR_BUILD_THREAD = -69.4 > Using MASTER_MYPORT = 9306 > Using MASTER_MYPORT1 = 9307 > Using SLAVE_MYPORT = 9308 > Using SLAVE_MYPORT1 = 9309 > Using SLAVE_MYPORT2 = 9310 > Killing Possible Leftover Processes > Sleep 1 second waiting for processes to die > Removing Stale Files > Creating Directories > ======================================================= > DEFAULT STORAGE ENGINE: innodb > TEST RESULT TIME (ms) > ------------------------------------------------------- > > > Servers started, exiting
Yep! That's exactly correct. > i just briefly perused this testing script, but it looks like you can > specify either valgrind or gdb for debugging? is dtrace supported with > this testing script? Haven't tried it yet... > is this the standard way for testing drizzle is through this interface? Yep. You can see a brief tutorial here: http://drizzle.org/wiki/Debugging_Drizzle_with_GDB > basically you can pass it test cases which are stored in a file, which > would normally be passed exactly on the command line? > > is there any existing documentation on the drizzle testing interface > (something to ask before asking all of the aforementioned questions, i > guess, sue me) > > m > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkm0RR8ACgkQ2upbWsB4UtFUaACeO0YW2zpx6/FGNhN0jcoaORNB uJIAnjnbUBigk4Pe9eyNdXaI4Y/F0+a5 =Fflo -----END PGP SIGNATURE----- _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
