Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 8CFFE19969 for ; Wed, 6 Apr 2016 20:23:26 +0000 (UTC) Received: (qmail 42719 invoked by uid 500); 6 Apr 2016 20:23:25 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 42582 invoked by uid 500); 6 Apr 2016 20:23:25 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 42525 invoked by uid 99); 6 Apr 2016 20:23:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Apr 2016 20:23:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 93B2C2C1F58 for ; Wed, 6 Apr 2016 20:23:25 +0000 (UTC) Date: Wed, 6 Apr 2016 20:23:25 +0000 (UTC) From: "Eric Badger (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MAPREDUCE-6658) TestMRJobs fails 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/MAPREDUCE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated MAPREDUCE-6658: ----------------------------------- Attachment: MAPREDUCE-6658.001.patch [~ajisakaa], I tracked down the issue. Indeed, it was my code that broke the tests. I'm not sure why I wasn't able to reproduce the failures consistently, but maybe that was another side effect of my earlier changes. The bug was that the MiniYARNCluster was explicitly calling transitionToActive on the resource manager with index 0. This overwrote some conf properties and reset the cluster max priority property back to DEFAULT. I'm attaching a patch that fixes this issue by only transition the RM with index 0 to active if we are in an HA cluster. > TestMRJobs fails > ---------------- > > Key: MAPREDUCE-6658 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6658 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: test > Reporter: Akira AJISAKA > Assignee: Eric Badger > Attachments: MAPREDUCE-6658.001.patch > > > TestMRJobs#testJobWithChangePriority fails. > {noformat} > Running org.apache.hadoop.mapreduce.v2.TestMRJobs > Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 446.855 sec <<< FAILURE! - in org.apache.hadoop.mapreduce.v2.TestMRJobs > testJobWithChangePriority(org.apache.hadoop.mapreduce.v2.TestMRJobs) Time elapsed: 21.477 sec <<< FAILURE! > java.lang.AssertionError: expected: but was: > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.apache.hadoop.mapreduce.v2.TestMRJobs.testJobWithChangePriority(TestMRJobs.java:276) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)