Subject: yarn nm builds breaking on 3.1 and 3.2


I'm seeing the yarn branch 3.1 and 3.2 builds breaking right now; one of
the patches is gone in the last 24 hours has done it.

[INFO] Finished at: 2019-10-09T18:18:31+01:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile
(default-testCompile) on project hadoop-yarn-server-nodemanager:
Compilation failure: Compilation failure:
[ERROR]
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/TestResourceMappings.java:[22,66]
package org.apache.hadoop.yarn.server.nodemanager.api.deviceplugin does not
exist
[ERROR]
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/TestResourceMappings.java:[41,15]
package Device does not exist
[ERROR]
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/container/TestResourceMappings.java:[49,15]
package Device does not exist
[ERROR] -> [Help 1]
[ERROR]
If I revert either branch to HADOOP-16491. Upgrade jetty version to 9.3.27
then everything works again;

I don't want to blindly revert all three; can someone take a a look and fix
these up, or, if there's no easy fix, pull the commit at fault.

thanks

Steve