Definitely a good catch.  Thanks for looking at this.
I'll make a note about this in our wiki as well - working on improving wiki
docs for testing.

On Sat, Jun 26, 2010 at 10:11 AM, Monty Taylor <email address hidden> wrote:

> Aha! Good catch there joe.
>
> The --enable options to configure change the list of default plugins.
> I'm not sure it's feasible to run the test suite with optional plugins
> enabled by default. The tests in the suite for optional plugins
> configure and set up the server properly for having that plugin enabled.
>
> Would it be possible in the gentoo build to remove the extra --enalbe
> options and only use --with instead?
>
> "Joe Daly" <email address hidden> wrote:
>
> >The logging_stats plugin changes users, in one test theres 500 users if
> >you had the auth-file-plugin enabled it would definately fail. I suspect
> >the other tests are a similiar failure.
> >
> >--
> >test suite failures
> >https://bugs.launchpad.net/bugs/598659
> >You received this bug notification because you are a member of Drizzle-
> >developers, which is subscribed to Drizzle.
> >
> >Status in A Lightweight SQL Database for Cloud and Web: New
> >Status in Gentoo Linux: New
> >
> >Bug description:
> >I have opened the topic of failing tests in 'answers' but the topic
> remains open for too long (
> https://answers.launchpad.net/drizzle/+question/114414).. A working
> testsuite is important for packaging drizzle on gentoo linux - it allows
> devs to catch runtime errors. Without it, drizzle releases are held back
> without reason. Follows a summary, more details in the 'answers' link above.
> >
> >Stopping All Servers
> >Failed 15/332 tests, 95.48% were successful.
> >
> >The log files in var/log may give you some hint
> >of what went wrong.
> >If you want to report this error, go to:
> >       http://bugs.launchpad.net/drizzle
> >The servers were restarted 48 times
> >Spent 2028.406 of 3279 seconds executing testcases
> >
> >mysql-test-run in default mode: *** Failing the test(s): main.connect
> main.data_dictionary_like_info main.drizzleslap main.information_schema
> main.lowercase_fs_off simple_user_policy.basic
> registry_dictionary.data_dictionary registry_dictionary.slap
> mysql_protocol.prototest logging_stats.command logging_stats.cumulative
> logging_stats.max_session logging_stats.max_user auth_test.basic
> auth_file.basic
> >
> >
> >
> >
> >
>
> --
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
>
> --
> test suite failures
> https://bugs.launchpad.net/bugs/598659
> You received this bug notification because you are a bug assignee.
>
> Status in A Lightweight SQL Database for Cloud and Web: New
> Status in Gentoo Linux: New
>
> Bug description:
> I have opened the topic of failing tests in 'answers' but the topic remains
> open for too long (https://answers.launchpad.net/drizzle/+question/114414).
> A working testsuite is important for packaging drizzle on gentoo linux - it
> allows devs to catch runtime errors. Without it, drizzle releases are held
> back without reason. Follows a summary, more details in the 'answers' link
> above.
>
> Stopping All Servers
> Failed 15/332 tests, 95.48% were successful.
>
> The log files in var/log may give you some hint
> of what went wrong.
> If you want to report this error, go to:
>        http://bugs.launchpad.net/drizzle
> The servers were restarted 48 times
> Spent 2028.406 of 3279 seconds executing testcases
>
> mysql-test-run in default mode: *** Failing the test(s): main.connect
> main.data_dictionary_like_info main.drizzleslap main.information_schema
> main.lowercase_fs_off simple_user_policy.basic
> registry_dictionary.data_dictionary registry_dictionary.slap
> mysql_protocol.prototest logging_stats.command logging_stats.cumulative
> logging_stats.max_session logging_stats.max_user auth_test.basic
> auth_file.basic
>
>
>
>
>