Return-Path: 
 <yarn-issues-return-1064-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 1A081D79A
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Fri, 12 Oct 2012 13:53:05 +0000 (UTC)
Received: (qmail 3088 invoked by uid 500); 12 Oct 2012 13:53:05 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 3047 invoked by uid 500); 12 Oct 2012 13:53:05 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 2917 invoked by uid 99); 12 Oct 2012 13:53:04 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Oct 2012 13:53:04 +0000
Date: Fri, 12 Oct 2012 13:53:04 +0000 (UTC)
From: "Thomas Graves (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <609171678.37191.1350049984879.JavaMail.jiratomcat@arcas>
In-Reply-To: <1888549218.26546.1349966343786.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (YARN-155) TestAppManager intermittently fails
 with jdk7
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Thomas Graves commented on YARN-155:
------------------------------------

The issue appears to be that the tests expect the initial app event type to be RMAppEventType.KILL and since with jdk7 the order of tests in random, the last test testRMAppSubmitError is sometimes being called before the others and it doesn't reset the type back to RMAppEventType.KILL.  I put in a @After routine to always reset it after each test.
                
> TestAppManager intermittently fails with jdk7
> ---------------------------------------------
>
>                 Key: YARN-155
>                 URL: https://issues.apache.org/jira/browse/YARN-155
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 0.23.3, 3.0.0, 2.0.3-alpha
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>              Labels: java7
>
> Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.851 sec <<< FAILURE!
> testRMAppSubmit(org.apache.hadoop.yarn.server.resourcemanager.TestAppManager)  Time elapsed: 0.017 sec  <<< FAILURE!
> junit.framework.AssertionFailedError: app event type is wrong before expected:<KILL> but was:<APP_REJECTED>
>         at junit.framework.Assert.fail(Assert.java:47)
>         at junit.framework.Assert.failNotEquals(Assert.java:283)
>         at junit.framework.Assert.assertEquals(Assert.java:64)
>         at org.apache.hadoop.yarn.server.resourcemanager.TestAppManager.setupDispatcher(TestAppManager.java:329)
>         at org.apache.hadoop.yarn.server.resourcemanager.TestAppManager.testRMAppSubmit(TestAppManager.java:354)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
> I can reproduce the failure on jdk6 if I move the testRMAppSubmit to the bottom of the file, so my initial hunch is this is due to test order.

--
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