You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Tae-Geon Um (JIRA)" <ji...@apache.org> on 2017/03/23 13:26:41 UTC
[jira] [Resolved] (REEF-1729) Fix test job timeouts in Travis CI
[ https://issues.apache.org/jira/browse/REEF-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tae-Geon Um resolved REEF-1729.
-------------------------------
Resolution: Fixed
Assignee: Tae-Geon Um (was: Sergiy Matusevych)
Fix Version/s: 0.16
Resolved via [PR#1268|https://github.com/apache/reef/pull/1268]
> Fix test job timeouts in Travis CI
> ----------------------------------
>
> Key: REEF-1729
> URL: https://issues.apache.org/jira/browse/REEF-1729
> Project: REEF
> Issue Type: Bug
> Reporter: Mariia Mykhailova
> Assignee: Tae-Geon Um
> Fix For: 0.16
>
>
> Recent changes in the way we're closing threads in Java code during REEF driver shutdown seem to have introduced a bug in this area. We observe transient test job timeouts in [Travis CI|https://travis-ci.org/apache/reef/builds/]: typically one test job takes 39-41 minutes, the limit on job duration is 50 minutes, and we're seeing test jobs hitting the limit and timing out. There is no test failure reported in such cases, so I suspect there is some runaway unaccounted for thread or an entire test which fails to complete properly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)