You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2017/03/28 04:45:41 UTC
[jira] [Commented] (APEXMALHAR-2284) POJOInnerJoinOperatorTest
fails in Travis CI
[ https://issues.apache.org/jira/browse/APEXMALHAR-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944524#comment-15944524 ]
Thomas Weise commented on APEXMALHAR-2284:
------------------------------------------
Any update on this? I see there is now even an example using this operator. I think we should either remove the operator or fix it?
> POJOInnerJoinOperatorTest fails in Travis CI
> --------------------------------------------
>
> Key: APEXMALHAR-2284
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2284
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Thomas Weise
> Assignee: Chaitanya
> Priority: Blocker
> Fix For: 3.7.0
>
>
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/166322754/log.txt
> {code}
> Failed tests:
> POJOInnerJoinOperatorTest.testEmitMultipleTuplesFromStream2:337 Number of tuple emitted expected:<2> but was:<4>
> POJOInnerJoinOperatorTest.testInnerJoinOperator:184 Number of tuple emitted expected:<1> but was:<2>
> POJOInnerJoinOperatorTest.testMultipleValues:236 Number of tuple emitted expected:<2> but was:<3>
> POJOInnerJoinOperatorTest.testUpdateStream1Values:292 Number of tuple emitted expected:<1> but was:<2>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)