Hi Martin great! So finally we found the cause! I think this is the most important thing. I had been a little bit superficiall because I started my test web server on a port where usually web servers run...I should use some other port (less popular)
Regards Andrea On 2/13/09, Robbie Gemmell <[email protected]> wrote: > Ah, the build machines...which run CruiseControl...which runs its dashboard > webserver on port 8080 by default...just like the wsdm tests... doh :P > > Apologies for not remembering that little nugget sooner, ill send you an > email off-list with corrective instructions hehe :) > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Martin Ritchie > Sent: 13 February 2009 17:05 > To: [email protected] > Subject: Re: WsDmAdapterTest Failure[MESSAGE NOT SCANNED] > > Andrea, > > I've attached the requested log fils (some text changed to protect the > inoccent) > > If it alright with you I'm going to disable the test at least for the > weekend as the build machines have been reporting failure for the last three > weeks and it would be good to get some positive emails from them. > > The CruiseControl machines I look after are doing this currently: > <snip> > > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Sent from my mobile device --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
