You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/02/18 00:48:13 UTC

[jira] [Commented] (TEZ-2058) Flaky test: TestTezJobs::testInvalidQueueSubmission

    [ https://issues.apache.org/jira/browse/TEZ-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325141#comment-14325141 ] 

Hadoop QA commented on TEZ-2058:
--------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12699351/TEZ-2058.1.patch
  against master revision ec7ad20.

    {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 test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/202//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/202//console

This message is automatically generated.

> Flaky test: TestTezJobs::testInvalidQueueSubmission
> ---------------------------------------------------
>
>                 Key: TEZ-2058
>                 URL: https://issues.apache.org/jira/browse/TEZ-2058
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>            Priority: Blocker
>         Attachments: TEZ-2058.1.patch
>
>
> Looks like there is a timing dependency introduced when running on a MiniCluster. Might have similar problems in real clusters. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)