"rabbitmq.variables" test is failing.

I do not think these two things are related.
1) The server's ability to start is not tied to passing 'make test'. Not passing 'make test' indicates that you likely don't have a server that is operating as it should, but it would still be able to start (depending on what/ how things failed). rabbitmq isn't critical to having an operating drizzle server.

2) The output you should pay attention to is here:
Plugin module
/usr/local/lib/drizzle7/libascii_plugin.so was compiled for version
20111129, which does not match the current running version of Drizzle:
20120130.
Couldn't load plugin library named 'ascii'.

Aborting:"Failed to initialize plugins". Abort was called from
drizzled/drizzled.cc:1341 in init_variables_after_daemonizing()

The problem is that the libascii plugin is for the previous release, though I do not know how this could have happened.

How did you build / install? Did you use the bzr source trees (it appears that way)?

yes i used bzr branch for this purpose... i took reference from: http://www.joinfu.com/2008/08/getting-a-working-c-c-plusplus-development-environment-for-developing-drizzle/

one of the problem fixed,, i manually updated the libascii files,, drizzle server has started working again,, but rabbitmq test is still failing.

Patrick: I've seen the rabbitmq failure too when building rpms. I didn't file a bug as I didn't know if it was something in the rpm script, but here it happens standalone. It seems to me a rabbitmq test is run even when rabbitmq isn't configured to build.

The libascii thing is of course completely unrelated.

On Fri, 20 Jan 2012 21:13:26 -0000, Henrik Ingo <email address hidden> wrote:
> Patrick: I've seen the rabbitmq failure too when building rpms. I didn't
> file a bug as I didn't know if it was something in the rpm script, but
> here it happens standalone. It seems to me a rabbitmq test is run even
> when rabbitmq isn't configured to build.
>
> The libascii thing is of course completely unrelated.

I have seen rabbitmq failures where (for example) the dev headers were
installed but no rabbitmq server.

--
Stewart Smith

Just confirming that rabbitmq.variables fails for me on a simple "make test".

henrik

Altered the bug description to accurately reflect the problem. Also seeing this issue.

This is failing if we don't have rabbitmq server installed.
Will see what we can do to ensure that we properly skip the test if we don't have what we need.