See <http://hudson.drizzle.org/job/drizzle-staging-randgen/325/>
This test is failing due to https://bugs.launchpad.net/drizzle/+bug/588408 This bug was also in MySQL, but my initial look showed me that the function that was patched in MySQL wasn't present in the drizzle code (was going to just patch it if it seemed crazy simple). As this test will be failing until this bug gets fixed, I was wondering if / how we ever disable tests and if you thought the failing test here should be. I noticed some randgen tests were commented out as needing investigation in the drizzle-automation config files - I'll be getting to these soon. This leads into my second question - I want to make sure bugs get assigned and don't just hang around neglected - is it sort of a grab-bag / whoever gets to it? If that is the case, do you guys have a preferred method of being asked / nagged to take a bug ; ) I have a couple of additional optimizer bugs that are unassigned in case anyone is just itching to do battle with that code. Thanks, Patrick
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
