You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@batchee.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2017/06/23 11:52:00 UTC
[jira] [Commented] (BATCHEE-118) Camel extension
checkJobWasExecutedSynchonously test fails
[ https://issues.apache.org/jira/browse/BATCHEE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16060777#comment-16060777 ]
Mark Struberg commented on BATCHEE-118:
---------------------------------------
I was able to reproduce the problem with IBM J9 1_7_0_64.
It seems to me that it's actually not a BatchEE problem but J9 cannot deal with Camel somehow?
> Camel extension checkJobWasExecutedSynchonously test fails
> ----------------------------------------------------------
>
> Key: BATCHEE-118
> URL: https://issues.apache.org/jira/browse/BATCHEE-118
> Project: BatchEE
> Issue Type: Bug
> Components: batchee-extensions
> Reporter: Scott Kurz
> Priority: Minor
>
> Pulled master (at commit 2891b07), found:
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.726 sec <<< FAILURE! - in org.apache.batchee.camel.component.JBatchComponentTest
> checkJobWasExecutedSynchonously on checkJobWasExecutedSynchonously(org.apache.batchee.camel.component.JBatchComponentTest)(org.apache.batchee.camel.component.JBatchComponentTest) Time elapsed: 0.843 sec <<< FAILURE!
> java.lang.AssertionError: expected:<JBatch-Camel> but was:<null>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.apache.batchee.camel.component.JBatchComponentTest.checkJobWasExecutedSynchonously(JBatchComponentTest.java:60)
> --
> Noticed it goes away if I add the wait for job to complete, but not having to wait seems the whole point of the test.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)