You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/07/08 18:44:05 UTC
[jira] [Commented] (PHOENIX-1528) Time out stuck tests
[ https://issues.apache.org/jira/browse/PHOENIX-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618900#comment-14618900 ]
Hadoop QA commented on PHOENIX-1528:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12687284/1528.txt
against master branch at commit 973bccb7019bfb0c15a9fd5259d7b01f37859b52.
ATTACHMENT ID: 12687284
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/116//console
This message is automatically generated.
> Time out stuck tests
> --------------------
>
> Key: PHOENIX-1528
> URL: https://issues.apache.org/jira/browse/PHOENIX-1528
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Attachments: 1528.txt
>
>
> We should have surefire kill tests that get stuck so the remainder of the suite can make progress. I propose a global timeout of 600 seconds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)