You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/08/14 18:15:45 UTC
[jira] [Updated] (SQOOP-2487) Sqoop2: ConnectorTestCase have wrong
order of arguments in assertEquals
[ https://issues.apache.org/jira/browse/SQOOP-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Jarcec Cecho updated SQOOP-2487:
--------------------------------------
Attachment: SQOOP-2487.patch
Attaching simple patch.
> 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)