[
https://issues.apache.org/jira/browse/SQOOP-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16705753#comment-16705753
]
ASF GitHub Bot commented on SQOOP-3393:
---------------------------------------
GitHub user dvoros reopened a pull request:
https://github.com/apache/sqoop/pull/63
SQOOP-3393 TestNetezzaExternalTableExportMapper hangs
Looks like this test only fails when run with all other uniTests. From the
logs I've found, that there's already a task_attempt directory (which we're
falling back to in absence of a `mapreduce.task.id`), and we're hanging because
of that. Most probably another test is creating that too.
The proposed solution is to simulate a unique `mapreduce.task.id` during
the tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dvoros/sqoop sqoop-3393
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sqoop/pull/63.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #63
----
commit 8c79b678f3a634562638408e68fb0845cbb7ca9b
Author: Daniel Voros <dvoros@...>
Date: 2018-11-29T19:56:57Z
reenable test to see what it does in travis
Change-Id: Ia62e1a5d85eafa900ecf260ee7167d6603c5dcfe
commit 9aefe2246618e5acb6a79eb62586e45c3cba30ee
Author: Daniel Voros <dvoros@...>
Date: 2018-11-29T22:50:09Z
unique task attempt dir during tests
Change-Id: Ica91a4578495ff5b9e0f23490411084403a03db1
----
> TestNetezzaExternalTableExportMapper hangs
> ------------------------------------------
>
> Key: SQOOP-3393
> URL: https://issues.apache.org/jira/browse/SQOOP-3393
> Project: Sqoop
> Issue Type: Bug
> Components: test
> Affects Versions: 1.5.0, 3.0.0
> Reporter: Daniel Voros
> Assignee: Daniel Voros
> Priority: Major
> Fix For: 1.5.0, 3.0.0
>
>
> Introduced in SQOOP-3378, spotted by [~vasas].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
