[
https://issues.apache.org/jira/browse/TEZ-3613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856610#comment-15856610
]
Jason Lowe commented on TEZ-3613:
---------------------------------
Sample stacktrace from timeout:
{noformat}
java.lang.Exception: test timed out after 5000 milliseconds
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901)
at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1295)
at java.net.InetAddress.getAllByName0(InetAddress.java:1248)
at java.net.InetAddress.getAllByName(InetAddress.java:1164)
at java.net.InetAddress.getAllByName(InetAddress.java:1098)
at java.net.InetAddress.getByName(InetAddress.java:1048)
at java.net.InetSocketAddress.<init>(InetSocketAddress.java:220)
at
org.apache.tez.dag.app.rm.TestTaskSchedulerManager.testReportFailureFromTaskScheduler(TestTaskSchedulerManager.java:581)
{noformat}
Maybe the test timeout is too short to accommodate any kind of network hiccup
in DNS?
> TestTaskSchedulerManager sporadically times out
> -----------------------------------------------
>
> Key: TEZ-3613
> URL: https://issues.apache.org/jira/browse/TEZ-3613
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jason Lowe
>
> Recent precommit builds show TestTaskSchedulerManager occasionally timing out
> in testReportFailureFromTaskScheduler.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
