[
https://issues.apache.org/jira/browse/HIVE-4853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707966#comment-13707966
]
Ashutosh Chauhan commented on HIVE-4853:
----------------------------------------
Increasing timeout probably is fine. However, I have noticed recently
timestamp1.q & timestamp2.q has started taking inordinately long time in my
builds. Sometimes more than an hour. They need to be looked closely.
> junit timeout needs to be updated
> ---------------------------------
>
> Key: HIVE-4853
> URL: https://issues.apache.org/jira/browse/HIVE-4853
> Project: Hive
> Issue Type: Bug
> Reporter: Gunther Hagleitner
> Assignee: Gunther Hagleitner
> Attachments: HIVE-4853.1.patch
>
>
> All the ptf, join etc tests we've added recently have pushed the junit time
> for TestCliDriver past the timout value on most machines (if run serially).
> The build machine uses it's own value - so you don't see it there. But when
> running locally it can be a real downer if you find out that the tests were
> aborted due to timeout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
