You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by dvoros <gi...@git.apache.org> on 2018/11/30 07:55:11 UTC
[GitHub] sqoop pull request #63: SQOOP-3393 TestNetezzaExternalTableExportMapper hang...
GitHub user dvoros opened 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 <dv...@...>
Date: 2018-11-29T19:56:57Z
reenable test to see what it does in travis
Change-Id: Ia62e1a5d85eafa900ecf260ee7167d6603c5dcfe
commit 9aefe2246618e5acb6a79eb62586e45c3cba30ee
Author: Daniel Voros <dv...@...>
Date: 2018-11-29T22:50:09Z
unique task attempt dir during tests
Change-Id: Ica91a4578495ff5b9e0f23490411084403a03db1
----
---
[GitHub] sqoop pull request #63: SQOOP-3393 TestNetezzaExternalTableExportMapper hang...
Posted by dvoros <gi...@git.apache.org>.
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 <dv...@...>
Date: 2018-11-29T19:56:57Z
reenable test to see what it does in travis
Change-Id: Ia62e1a5d85eafa900ecf260ee7167d6603c5dcfe
commit 9aefe2246618e5acb6a79eb62586e45c3cba30ee
Author: Daniel Voros <dv...@...>
Date: 2018-11-29T22:50:09Z
unique task attempt dir during tests
Change-Id: Ica91a4578495ff5b9e0f23490411084403a03db1
----
---
[GitHub] sqoop pull request #63: SQOOP-3393 TestNetezzaExternalTableExportMapper hang...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/sqoop/pull/63
---
[GitHub] sqoop issue #63: SQOOP-3393 TestNetezzaExternalTableExportMapper hangs
Posted by dvoros <gi...@git.apache.org>.
Github user dvoros commented on the issue:
https://github.com/apache/sqoop/pull/63
Thanks for the review @szvasas and for the reopening tip, just did that. 🤞
---
[GitHub] sqoop pull request #63: SQOOP-3393 TestNetezzaExternalTableExportMapper hang...
Posted by dvoros <gi...@git.apache.org>.
Github user dvoros closed the pull request at:
https://github.com/apache/sqoop/pull/63
---