[
https://issues.apache.org/jira/browse/SQOOP-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179191#comment-15179191
]
Jarek Jarcec Cecho commented on SQOOP-2865:
-------------------------------------------
{{ParquetTest}} is known to be flaky and {{S3Test}} is not really failing but
it's not running at all - it seems that this change has helped :) The total
running time of the integration tests was:
{code}
[INFO] Total time: 01:12 h
{code}
Since I've changed the configuration to time out after hour and half, we have
another ~18 minutes of buffer right now.
> Sqoop2: Increase test timeout from one hour
> -------------------------------------------
>
> Key: SQOOP-2865
> URL: https://issues.apache.org/jira/browse/SQOOP-2865
> 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-2865.patch
>
>
> Our integration tests are currently running with [one hour
> timeout|https://github.com/apache/sqoop/blob/sqoop2/pom.xml#L796]. That seems
> fine on my laptop, but Apache build slaves seems to be slower and the build
> is quite frequently timing out. I don't see a need to limit the number of
> tests as I would much rather have better quality then faster tests, so I
> would like to propose to increase the timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
