[
https://issues.apache.org/jira/browse/SQOOP-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700209#comment-14700209
]
ASF subversion and git services commented on SQOOP-2487:
--------------------------------------------------------
Commit 58b2d1c1c43874014b68a03b46c1ef51aa0dd3d7 in sqoop's branch
refs/heads/sqoop2 from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=58b2d1c ]
SQOOP-2487: Sqoop2: ConnectorTestCase have wrong order of arguments in
assertEquals
(Jarek Jarcec Cecho via Abraham Elmahrek)
> Sqoop2: ConnectorTestCase have wrong order of arguments in assertEquals
> -----------------------------------------------------------------------
>
> Key: SQOOP-2487
> URL: https://issues.apache.org/jira/browse/SQOOP-2487
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.6
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2487.patch
>
>
> While investigating precommit hook failures, I've noticed that
> {{ConnectorTestCase}} is using wrong order of arguments in {{assertX}}
> methods leading to a funny exceptions:
> {code}
> AllTypesTest.testFrom:110->ConnectorTestCase.executeJob:300->ConnectorTestCase.executeJob:289
> Submission finished with error: null expected [FAILED] but found [SUCCEEDED]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
