This test case has been broken by
Its because there was a new config added in that JIRA yarn.cluster.max-application-priority which was not added in yarn-default.xml
But I think the main problem here is that YarnConfiguration.java is in hadoop-yarn-api and the test is in hadoop-yarn-common.
Either we should add this test class in hadoop-yarn-api or we shoud make sure that Jenkins runs this test in hadoop-yarn-common if YarnConfiguration.java is changed.
Otherwise we will keep on getting this test failure after commits.
Is there a reason tests are not there in hadoop-yarn-api ?
cc Akira Ajisaka, Sunil G