I was about to start trying to build 2.17.3, but there are some test failures in camel-core which I think need to be looked at first:
Jenkins is showing one of the failures: https://builds.apache.org/view/A-D/view/Camel/job/Camel.2.17.x.fulltest/org.apache.camel$camel-core/132/testReport/org.apache.camel.component.file/FileComponentConfigurationAndDocumentationTest/testComponentConfiguration/ <https://builds.apache.org/view/A-D/view/Camel/job/Camel.2.17.x.fulltest/org.apache.camel$camel-core/132/testReport/org.apache.camel.component.file/FileComponentConfigurationAndDocumentationTest/testComponentConfiguration/> I can reproduce that 100% on my machine. I’m also getting: Running org.apache.camel.UnitOfWorkSyncProcessTest Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.905 sec <<< FAILURE! - in org.apache.camel.UnitOfWorkSyncProcessTest testUnitOfWorkSync(org.apache.camel.UnitOfWorkSyncProcessTest) Time elapsed: 0.528 sec <<< FAILURE! junit.framework.AssertionFailedError: expected not same at org.apache.camel.UnitOfWorkSyncProcessTest.testUnitOfWorkSync(UnitOfWorkSyncProcessTest.java:58) testUnitOfWorkSync(org.apache.camel.UnitOfWorkSyncProcessTest) Time elapsed: 0.125 sec <<< FAILURE! junit.framework.AssertionFailedError: expected not same at org.apache.camel.UnitOfWorkSyncProcessTest.testUnitOfWorkSync(UnitOfWorkSyncProcessTest.java:58) testUnitOfWorkSync(org.apache.camel.UnitOfWorkSyncProcessTest) Time elapsed: 0.121 sec <<< FAILURE! junit.framework.AssertionFailedError: expected not same at org.apache.camel.UnitOfWorkSyncProcessTest.testUnitOfWorkSync(UnitOfWorkSyncProcessTest.java:58) Results : Failed tests: org.apache.camel.UnitOfWorkSyncProcessTest.testUnitOfWorkSync(org.apache.camel.UnitOfWorkSyncProcessTest) Run 1: UnitOfWorkSyncProcessTest>TestSupport.runBare:58->testUnitOfWorkSync:58 expected not same Run 2: UnitOfWorkSyncProcessTest>TestSupport.runBare:58->testUnitOfWorkSync:58 expected not same Run 3: UnitOfWorkSyncProcessTest>TestSupport.runBare:58->testUnitOfWorkSync:58 expected not same Does anyone have any idea if there is a fix from master that needs to be pulled back or similar? Thanks! -- Daniel Kulp dk...@apache.org <mailto:dk...@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog> Talend Community Coder - http://coders.talend.com <http://coders.talend.com/>
