Looking at the reason for the build failure I am questioning the
existence of performance tests within our regular build test suite. We
e.g. have StreamingSpeed and StreamingCapacity tests with the later one
failing. It's definitely nice to have them but executing them as part of
a frequent build on an unpredictable build system seems to be
inappropriate IMO. How about deactivating them?
-Andreas
Bamboo [DEV] wrote:
> The project Mule - Mule 2.0.x (JDK1.5) has the following 1 change by 1 author:
>
> *Andreas Guenther* made the following changes at
>
> Comment:
> MULE-3318 - Changing the issue number since reason for failure changed an will be addressed in new issue.
>
>
>> /branches/mule-2.0.x/transports/vm/src/test/resources/mule-test-exclusions.txt (11719)
>>
>
>
>
> ---------------------------------------------------------------------------------------
>
> The build has 1 failed test and 2223 successful tests.
>
> Click
http://bamboo.mulesource.org/browse/MULE-MULEV20X-492 to find out more.
>
> Thanks,
>
> Bamboo
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
