Hi Willem,

I use the following environments for building Camel:

1)
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a;
2013-09-17 11:22:22-0400)
Java version: 1.7.0_55, vendor: Oracle Corporation
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"

-> After patching
DefaultTraceEventMessageTest.testDefaultTraceEventMessageBody and
disabling PrinterPrintTest.setJobName I was able to run all tests,
although numerous attempts were needed because of sporadic test
failures (especially in camel-jgroups and camel-ftp).

2)
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a;
2013-09-17 11:22:22-0400)
Java version: 1.7.0_55, vendor: Oracle Corporation
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

-> Fails to build due to test error in camel-ftp/SftpChmodTest.

3)
Apache Maven 3.0.5
Java version: 1.7.0_55, vendor: Oracle Corporation
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-24-generic", arch: "amd64", family: "unix"
(Ubuntu Linux 14.04 x86_64, kernel 3.13.0-24)

-> Fails to build due to test errors in
camel-core/OptimisticLockRetryPolicyTest.

Do you also experience test failures when building Camel on your local
machine? What platform do you use?

Thanks,
Gregor


On Wed, May 14, 2014 at 5:03 AM, Willem Jiang <willem.ji...@gmail.com> wrote:
> Hi Gregor,
>
> It could be more easy to run the tests if you are using oracle lasted JDK 7.
>
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
> On May 14, 2014 at 4:10:41 PM, Gregor Zurowski (gre...@zurowski.org) wrote:
>> Hi Everyone:
>>
>>
>> During the last vote for releasing version 2.13.1 it seemed that most of
>> you who voted use OS X as the primary platform for building Camel locally.
>> My primary development platforms are Windows and Linux, and I actually had
>> to struggle a bit to get all JUnit tests executed. As posted in the voting
>> thread, I had to modify two tests
>> (DefaultTraceEventMessageTest.testDefaultTraceEventMessageBody [1] and
>> PrinterPrintTest.setJobName) that would obviously not run on Windows at
>> all. What I also experienced is that some tests fail sporadically
>> (especially tests in camel-jgroups and camel-ftp seem to fail often). After
>> numerous attempts, I was eventually able to build on Windows without test
>> failures. I was not able to build on Ubuntu Linux 14.04 with Java 7 though.
>>
>>
>> Before going into further details I want to understand whether these
>> sporadic test failures could be platform related or whether you also
>> experience these when building locally?
>>
>>
>> Thanks in advance,
>>
>> Gregor
>>
>>
>>
>> [1]
>> https://github.com/apache/camel/commit/48923c5ae8e2a6247f44306ab272634466b4d053
>>
>

Reply via email to