[Mono-dev] Branching for Mono 2.6.0 on September 24th...
mike at middlesoft.co.uk
Mon Sep 21 17:10:59 EDT 2009
I was going to GUIDs or something similar so as part of the queue name
so that each test will use a unique queue. At the moment there is a
bit of an issue where if the tests fail, subsequent runs will also
fail until RabbitMQ has been reset (i.e. all of the queues flushed
out) and this change should also ensure that concurrent access to the
same box should not be an issue.
On Mon, Sep 21, 2009 at 9:29 PM, Andrew Jorgensen <ajorgensen at novell.com> wrote:
> On Fri, 2009-09-18 at 17:35 +0100, Michael Barker wrote:
>> > So the default installation is enough for the System.Messaging tests.
>> > At Novell we have multiple build machines running and it doesn't make sense
>> > to install
>> > RabbitMQ on all of them, so can we use a single remote instance for those
>> > tests? Will
>> > the test suite work if ran in parallel all targeting the same RabbitMQ
>> > instance?
>> I will have to tweak to unit tests so that will work, but it is
>> reasonably straight forward. The host used for messaging is specified
>> as part of the queue name, so I will need to read a host name
>> configuration value from somewhere. Where would be easiest for you
>> (environment variable)?
> Sorry for not answering earlier. Environment variable would be perfect
> for me. Will this work sanely if multiple hosts are running the tests
> at the same time?
More information about the Mono-devel-list