{"issue":{"created_at":"2011-12-04T14:36:34Z","state":"open","updated_at":"2011-12-05T14:03:15Z","user":{"gravatar_id":"809e49872e79afb7d9b077b9742da515","id":1168602,"url":"https://api.github.com/users/lecstor","login":"lecstor","avatar_url":"https://secure.gravatar.com/avatar/809e49872e79afb7d9b077b9742da515?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"comments":5,"body":"ok, so I went to add documentation, thought that would be easier if there was a method to document, and added the method. While implementing that I thought I found a different angle but that didn't pan out.. but by then I was determined to find a reliable way to produce the errors. I tried multiple copies of 02-initialise-schema.t but they ran fine. Multiple copies of replication-mysql fails reliably for me, even when only running 3 in parallel.\r\nI think it comes down to the time it takes mysql to start answering on that port from when you call Test::mysqld. I'd be interested to know if you can replicate the issues I'm seeing.\r\nApart from the port issue, the other error I'm seeing is:\r\n\r\n            (in cleanup) DBIx::Class::Storage::DBI::__ANON__(): DBI Exception: DBD::mysql::db do failed: Unknown table 'cd_artist' [for Statement \"drop table cd_artist\"] at /home/edoc/dev/apps/Test-DBIx-Class/lib/Test/DBIx/Class/SchemaManager.pm line 201\r\n\r\nI'm not sure if they're related.\r\n\r\n","assignee":null,"id":2442061,"pull_request":{"patch_url":"https://github.com/jjn1056/Test-DBIx-Class/pull/9.patch","html_url":"https://github.com/jjn1056/Test-DBIx-Class/pull/9","diff_url":"https://github.com/jjn1056/Test-DBIx-Class/pull/9.diff"},"labels":[],"number":9,"title":"Overload","html_url":"https://github.com/jjn1056/Test-DBIx-Class/issues/9","closed_at":null,"url":"https://api.github.com/repos/jjn1056/Test-DBIx-Class/issues/9","milestone":null},"action":"created","comment":{"created_at":"2011-12-05T14:03:15Z","updated_at":"2011-12-05T14:03:15Z","user":{"gravatar_id":"1279d6bd0b4754cd7e879507c92b26f6","id":67652,"url":"https://api.github.com/users/jjn1056","login":"jjn1056","avatar_url":"https://secure.gravatar.com/avatar/1279d6bd0b4754cd7e879507c92b26f6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"hey,\r\n\r\nSo unless you object I will likely pull your test code into my master branch, but put the tests under author only level testing.  I think this kind of thing is useful as I try to ponder a more permanent fix.  Just let me know if you are cool with that.  I'll probably also make the tempdir thing optional for the next release, so we have the feature in place for when we have it merged up in testmysql\r\n\r\nBTW, quick question.  How are you finding doing development one TDBIC?  I just just because I recently started using a home grown wrapper on Module::Install (that's in maint/Maker.pm) and I wonder if the approach is easy to pick up.  Lots of people are using DistZilla, but that is pretty heavyweight and seems to arose passions both for and against.   Module;:Install out of the box seems to be a bit confusing, so my Maker.pm wrapper trys to help with that.  Was I successful?\r\n\r\nThanks John","id":3017280,"url":"https://api.github.com/repos/jjn1056/Test-DBIx-Class/issues/comments/3017280"}}