[YARN-8730] TestRMWebServiceAppsNodelabel#testAppsRunning fails

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.4
• Fix Version/s: 2.8.5
• Component/s: resourcemanager
• Target Version/s: 2.8.5
• Hadoop Flags: Reviewed
• Assignee: Eric Payne
• Reporter: Jason Darrell Lowe
• Created: 29/Aug/18 22:42
• Updated: 14/Oct/19 15:38
• Resolved: 05/Sep/18 22:37

Description

TestRMWebServiceAppsNodelabel is failing in branch-2.8:

Running org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServiceAppsNodelabel
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.473 sec <<< FAILURE! - in org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServiceAppsNodelabel
testAppsRunning(org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServiceAppsNodelabel)  Time elapsed: 6.708 sec  <<< FAILURE!
org.junit.ComparisonFailure: partition amused expected:<{"[]memory":1024,"vCores...> but was:<{"[res":{"memory":1024,"memorySize":1024,"virtualCores":1},"]memory":1024,"vCores...>
	at org.junit.Assert.assertEquals(Assert.java:115)
	at org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServiceAppsNodelabel.verifyResource(TestRMWebServiceAppsNodelabel.java:222)
	at org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServiceAppsNodelabel.testAppsRunning(TestRMWebServiceAppsNodelabel.java:205)

Issue Links

• is caused by: YARN-7619 Max AM Resource value in Capacity Scheduler UI has to be refreshed for every user