Failed: YARN-3344 PreCommit Build #6983
Jira: https://issues.apache.org/jira/browse/YARN-3344
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6983/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3122 lines...]
/bin/grep:
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patch:
No such file or directory
cat: /tmp/tmp.modules.14330: No such file or directory
rm: cannot remove '/tmp/tmp.modules.14330': No such file or directory
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704878/YARN-3344-branch-2.6.0.001.patch
against trunk revision 2681ed9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:red}-1 eclipse:eclipse{color}. The patch failed to build with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6983//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6983//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
12217aa791e2f8a281e89d7896315807e0e51d03 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
Failed: YARN-3288 PreCommit Build #6989
Jira: https://issues.apache.org/jira/browse/YARN-3288
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6989/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 23 lines...]
==
==
Testing patch for YARN-3288.
==
==
HEAD is now at 5608520 YARN-3339. TestDockerContainerExecutor should pull a
single image and not the entire centos repository. (Ravindra Kumar Naik via
raviprak)
Previous HEAD position was 5608520... YARN-3339. TestDockerContainerExecutor
should pull a single image and not the entire centos repository. (Ravindra
Kumar Naik via raviprak)
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 5 commits, and can be fast-forwarded.
(use git pull to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 56085203c43b8f2561bf3745910e03f8ac176a67.
YARN-3288 patch is being downloaded at Tue Mar 17 00:30:24 UTC 2015 from
http://issues.apache.org/jira/secure/attachment/12703208/YARN-3288.01.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12703208/YARN-3288.01.patch
against trunk revision 5608520.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6989//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
c0e626a44ddffba53036b5074212ab066af3b9ac logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
Success: YARN-3344 PreCommit Build #6986
Jira: https://issues.apache.org/jira/browse/YARN-3344
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6986/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3317 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704909/YARN-3344-branch-trunk.003.patch
against trunk revision 2681ed9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6986//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6986//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
55c366b8a6937babd7babde927a55dbff208ab0a logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6984
Archived 15 artifacts
Archive block size is 32768
Received 60 blocks and 7074384 bytes
Compression is 21.7%
Took 1.7 sec
Description set: YARN-3344
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6985
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Success: YARN-3288 PreCommit Build #6991
Jira: https://issues.apache.org/jira/browse/YARN-3288
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6991/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3456 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704947/YARN-3288.02.patch
against trunk revision 5608520.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6991//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6991//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
55361616dd9cf6779958ffb9ddc7abd314b6da1b logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6986
Archived 15 artifacts
Archive block size is 32768
Received 64 blocks and 6869860 bytes
Compression is 23.4%
Took 1.5 sec
Description set: YARN-3288
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6990
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-3284 PreCommit Build #6987
Jira: https://issues.apache.org/jira/browse/YARN-3284 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6987/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 3155 lines...] == == Determining number of patched release audit warnings. == == /home/jenkins/tools/maven/latest/bin/mvn apache-rat:check -DHadoopPatchProcess /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patchReleaseAuditOutput.txt 21 There appear to be 0 release audit warnings after applying the patch. == == Running tests. == == Running tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient /home/jenkins/tools/maven/latest/bin/mvn clean install -fn -Pnative -Drequire.test.libhadoop -DHadoopPatchProcess FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:742) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at com.sun.proxy.$Proxy120.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:956) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.build(Build.java:198) at hudson.model.Build$BuildExecution.doRun(Build.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:805) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.init(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.init(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ### ## FAILED TESTS (if any) ## No tests ran.
Failed: YARN-3205 PreCommit Build #6992
Jira: https://issues.apache.org/jira/browse/YARN-3205
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6992/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3116 lines...]
cat:
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt:
No such file or directory
awk: cannot open
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt
(No such file or directory)
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704957/YARN-3205.000.patch
against trunk revision 5608520.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6992//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6992//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6992//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
67d51c571c6270dd73929fe9a24a7b9862eeb33b logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6991
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-3305 PreCommit Build #6990
Jira: https://issues.apache.org/jira/browse/YARN-3305
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6990/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3474 lines...]
http://issues.apache.org/jira/secure/attachment/12704939/0003-YARN-3305.patch
against trunk revision 5608520.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6990//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6990//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6990//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
c83e77e4cd23fe2e1ae369b37fdc2931463293c7 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6986
Archived 15 artifacts
Archive block size is 32768
Received 52 blocks and 7380822 bytes
Compression is 18.8%
Took 1.6 sec
[description-setter] Could not determine description.
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6988
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
1 tests failed.
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartGetApplicationList[1]
Error Message:
rMAppManager.logApplicationSummary(
isA(org.apache.hadoop.yarn.api.records.ApplicationId)
);
Wanted 3 times:
- at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartGetApplicationList(TestRMRestart.java:969)
But was 2 times:
- at
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.handle(RMAppManager.java:66)
Stack Trace:
org.mockito.exceptions.verification.TooLittleActualInvocations:
rMAppManager.logApplicationSummary(
isA(org.apache.hadoop.yarn.api.records.ApplicationId)
);
Wanted 3 times:
- at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartGetApplicationList(TestRMRestart.java:969)
But was 2 times:
- at
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.handle(RMAppManager.java:66)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartGetApplicationList(TestRMRestart.java:969)
Success: YARN-2556 PreCommit Build #6988
Jira: https://issues.apache.org/jira/browse/YARN-2556
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6988/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3128 lines...]
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6988//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6988//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
f31c8a00b700c149a9d9b8aaecaf94c35ad4cac4 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6986
ERROR: Failed to archive
{patchprocess/patchJavacWarnings.txt=patchprocess/patchJavacWarnings.txt,
patchprocess/trunkJavacWarnings.txt=patchprocess/trunkJavacWarnings.txt,
patchprocess/filteredTrunkJavacWarnings.txt=patchprocess/filteredTrunkJavacWarnings.txt,
patchprocess/trunkJavadocWarnings.txt=patchprocess/trunkJavadocWarnings.txt,
patchprocess/patchJavadocWarnings.txt=patchprocess/patchJavadocWarnings.txt,
patchprocess/filteredPatchJavacWarnings.txt=patchprocess/filteredPatchJavacWarnings.txt}
due to internal error; falling back to full archiving
java.lang.IllegalStateException: checksum mismatch after transfer
(6577874794637500426 vs. 2980377180);
/x1/jenkins/jenkins-home/jobs/PreCommit-YARN-Build/builds/2015-03-16_23-10-18/archive/patchprocess/patchJavadocWarnings.txt
may be corrupted
at jsync.protocol.FileSequenceReader.read(FileSequenceReader.java:45)
at
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.remoteSync(JSyncArtifactManager.java:145)
at
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.archive(JSyncArtifactManager.java:68)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
at
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
at hudson.model.Build$BuildExecution.post2(Build.java:182)
at
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
at hudson.model.Run.execute(Run.java:1731)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Description set: YARN-2556
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6987
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-3341 PreCommit Build #6985
Jira: https://issues.apache.org/jira/browse/YARN-3341
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6985/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3469 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704913/YARN-3341.001.patch
against trunk revision 2681ed9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6985//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6985//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6985//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
d5bc6fa3425030c06d21b4f97e6567afd3429776 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6984
Archived 15 artifacts
Archive block size is 32768
Received 60 blocks and 7096254 bytes
Compression is 21.7%
Took 1.6 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-3345 PreCommit Build #6980
Jira: https://issues.apache.org/jira/browse/YARN-3345
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6980/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3839 lines...]
http://issues.apache.org/jira/secure/attachment/12704847/YARN-3345.2.patch
against trunk revision ed4e72a.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 2.0.3) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1
release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.api.TestPBImplRecords
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6980//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6980//artifact/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6980//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6980//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
864186d0dd84249c36cc871e3fd863bd0730629d logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6979
Archived 26 artifacts
Archive block size is 32768
Received 42 blocks and 7585747 bytes
Compression is 15.4%
Took 3.2 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
1 tests failed.
FAILED:
org.apache.hadoop.yarn.api.TestPBImplRecords.testSetNodeLabelsAttributesRequestPBImpl
Error Message:
hashCode not designed
Stack Trace:
java.lang.AssertionError: hashCode not designed
at
org.apache.hadoop.yarn.api.records.impl.pb.NodeLabelAttributesPBImpl.hashCode(NodeLabelAttributesPBImpl.java:123)
at java.lang.Object.toString(Object.java:237)
at java.lang.String.valueOf(String.java:2854)
at java.lang.StringBuilder.append(StringBuilder.java:128)
at java.util.AbstractCollection.toString(AbstractCollection.java:458)
at java.util.Formatter$FormatSpecifier.printString(Formatter.java:2838)
at java.util.Formatter$FormatSpecifier.print(Formatter.java:2718)
at java.util.Formatter.format(Formatter.java:2488)
at java.util.Formatter.format(Formatter.java:2423)
at java.lang.String.format(String.java:2797)
at
org.apache.hadoop.yarn.api.TestPBImplRecords.getGetSetPairs(TestPBImplRecords.java:573)
at
org.apache.hadoop.yarn.api.TestPBImplRecords.validatePBImplRecord(TestPBImplRecords.java:587)
at
org.apache.hadoop.yarn.api.TestPBImplRecords.testSetNodeLabelsAttributesRequestPBImpl(TestPBImplRecords.java:1294)
Re: Distributed shell with host affinity and relaxLocality
Hey Chris What scheduler/version is this? On Mon, Mar 16, 2015 at 12:01 PM, Chris Riccomini criccom...@linkedin.com.invalid wrote: Hey all, We have been testing YARN with host-specific ContainerRequests. For our tests, we've been using the DistributedShell example. We've applied YARN-1974, which allows us to specify node lists, relax locality, etc. Everything seems to work as expected when we have relaxLocality set to false, and we request a specific host. When we set relaxLocality to true, things get weird. We run three nodes: node1, node2, and node3. When we start DistributedShell with, we configure it (via CLI params) to use two containers, and have a host-level request for node3. What we observe is that the AM and one container both end up on node2, and a third container ends up on node3. There are enough resources for node3 to handle both containers, but the second one doesn't end up there. We also notice that the DistributedShell app wedges because the container on node3 never completes. What is the expected behavior here? This seems to be broken. Cheers, Chris -- Karthik Kambatla Software Engineer, Cloudera Inc. http://five.sentenc.es
Re: Distributed shell with host affinity and relaxLocality
+ Navina Hey Karthik, YARN 2.6.0 FairShare. Cheers, Chris On 3/16/15 1:28 PM, Karthik Kambatla ka...@cloudera.com wrote: Hey Chris What scheduler/version is this? On Mon, Mar 16, 2015 at 12:01 PM, Chris Riccomini criccom...@linkedin.com.invalid wrote: Hey all, We have been testing YARN with host-specific ContainerRequests. For our tests, we've been using the DistributedShell example. We've applied YARN-1974, which allows us to specify node lists, relax locality, etc. Everything seems to work as expected when we have relaxLocality set to false, and we request a specific host. When we set relaxLocality to true, things get weird. We run three nodes: node1, node2, and node3. When we start DistributedShell with, we configure it (via CLI params) to use two containers, and have a host-level request for node3. What we observe is that the AM and one container both end up on node2, and a third container ends up on node3. There are enough resources for node3 to handle both containers, but the second one doesn't end up there. We also notice that the DistributedShell app wedges because the container on node3 never completes. What is the expected behavior here? This seems to be broken. Cheers, Chris -- Karthik Kambatla Software Engineer, Cloudera Inc. http://five.sentenc.es
[jira] [Created] (YARN-3351) AppMaster tracking URL is broken in HA
Anubhav Dhoot created YARN-3351:
---
Summary: AppMaster tracking URL is broken in HA
Key: YARN-3351
URL: https://issues.apache.org/jira/browse/YARN-3351
Project: Hadoop YARN
Issue Type: Bug
Components: webapp
Reporter: Anubhav Dhoot
Assignee: Anubhav Dhoot
After YARN-2713, the AppMaster link is broken in HA.
The log and full stack trace is shown below
{noformat}
2015-02-05 20:47:43,478 WARN org.mortbay.log:
/proxy/application_1423182188062_0002/: java.net.BindException: Cannot assign
requested address
{noformat}
{noformat}
java.net.BindException: Cannot assign requested address
at java.net.PlainSocketImpl.socketBind(Native Method)
at
java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
at java.net.Socket.bind(Socket.java:631)
at java.net.Socket.init(Socket.java:423)
at java.net.Socket.init(Socket.java:280)
at
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80)
at
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122)
at
org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
at
org.apache.hadoop.yarn.server.webproxy.WebAppProxyServlet.proxyLink(WebAppProxyServlet.java:188)
at
org.apache.hadoop.yarn.server.webproxy.WebAppProxyServlet.doGet(WebAppProxyServlet.java:345)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1221)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: YARN-1453 PreCommit Build #6972
Jira: https://issues.apache.org/jira/browse/YARN-1453
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6972/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 5021 lines...]
against trunk revision 3ff1ba2.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-registry
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-web-proxy:
org.apache.hadoop.yarn.server.resourcemanager.TestRM
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6972//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6972//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6972//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
92c47f2df8f636df417f106c55b483e79c45cd55 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6957
Archived 55 artifacts
Archive block size is 32768
Received 52 blocks and 8712748 bytes
Compression is 16.4%
Took 3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
1 tests failed.
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.TestRM.testAppOnMultiNode[0]
Error Message:
test timed out after 3 milliseconds
Stack Trace:
java.lang.Exception: test timed out after 3 milliseconds
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901)
at
java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1293)
at java.net.InetAddress.getAllByName0(InetAddress.java:1246)
at java.net.InetAddress.getAllByName(InetAddress.java:1162)
at java.net.InetAddress.getAllByName(InetAddress.java:1098)
at java.net.InetAddress.getByName(InetAddress.java:1048)
at
org.apache.hadoop.security.SecurityUtil$QualifiedHostResolver.getInetAddressByName(SecurityUtil.java:599)
at
org.apache.hadoop.security.SecurityUtil$QualifiedHostResolver.getByExactName(SecurityUtil.java:572)
at
org.apache.hadoop.security.SecurityUtil$QualifiedHostResolver.getByName(SecurityUtil.java:553)
at
org.apache.hadoop.security.SecurityUtil.getByName(SecurityUtil.java:465)
at
org.apache.hadoop.net.NetUtils.createSocketAddrForHost(NetUtils.java:237)
at
Hadoop-Yarn-trunk - Build # 868 - Failure
See https://builds.apache.org/job/Hadoop-Yarn-trunk/868/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7204 lines...] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.558 sec - in org.apache.hadoop.yarn.server.nodemanager.webapp.TestNMWebServicesApps Running org.apache.hadoop.yarn.server.nodemanager.webapp.TestNMWebServer Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.568 sec - in org.apache.hadoop.yarn.server.nodemanager.webapp.TestNMWebServer Results : Tests in error: TestResourceLocalizationService.cleanup:186 » IO Unable to delete directory ta... Tests run: 288, Failures: 0, Errors: 1, Skipped: 8 [INFO] [INFO] Reactor Summary: [INFO] [INFO] hadoop-yarn ... SUCCESS [ 3.291 s] [INFO] hadoop-yarn-api ... SUCCESS [03:14 min] [INFO] hadoop-yarn-common SUCCESS [02:52 min] [INFO] hadoop-yarn-server SUCCESS [ 0.093 s] [INFO] hadoop-yarn-server-common . SUCCESS [ 42.267 s] [INFO] hadoop-yarn-server-nodemanager FAILURE [05:34 min] [INFO] hadoop-yarn-server-web-proxy .. SKIPPED [INFO] hadoop-yarn-server-applicationhistoryservice .. SKIPPED [INFO] hadoop-yarn-server-resourcemanager SKIPPED [INFO] hadoop-yarn-server-tests .. SKIPPED [INFO] hadoop-yarn-client SKIPPED [INFO] hadoop-yarn-server-sharedcachemanager . SKIPPED [INFO] hadoop-yarn-applications .. SKIPPED [INFO] hadoop-yarn-applications-distributedshell . SKIPPED [INFO] hadoop-yarn-applications-unmanaged-am-launcher SKIPPED [INFO] hadoop-yarn-site .. SKIPPED [INFO] hadoop-yarn-registry .. SKIPPED [INFO] hadoop-yarn-project ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 12:29 min [INFO] Finished at: 2015-03-16T10:44:44+00:00 [INFO] Final Memory: 75M/1151M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project hadoop-yarn-server-nodemanager: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :hadoop-yarn-server-nodemanager Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Updating YARN-3171 Sending e-mails to: yarn-dev@hadoop.apache.org Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 1 tests failed. REGRESSION: org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService.testPublicResourceInitializesLocalDir Error Message: Unable to delete directory target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService/1/filecache. Stack Trace: java.io.IOException: Unable to delete directory target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService/1/filecache. at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1541) at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2270) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) at org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2270) at org.apache.commons.io.FileUtils.cleanDirectory(FileUtils.java:1653) at org.apache.commons.io.FileUtils.deleteDirectory(FileUtils.java:1535) at
Build failed in Jenkins: Hadoop-Yarn-trunk #868
See https://builds.apache.org/job/Hadoop-Yarn-trunk/868/changes Changes: [xgong] YARN-3171. Sort by Application id, AppAttempt and ContainerID doesn't -- [...truncated 7011 lines...] [exec]char *resources, *resources_key, *resources_value; [exec] ^ [exec] https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/main.c:116:21: warning: unused variable 'resources_key' [-Wunused-variable] [exec]char *resources, *resources_key, *resources_value; [exec] ^ [exec] /home/jenkDependee https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarnins/jenkins-slave/workspace/Hadoop-Yarn-trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/-server-nodemanager/target/native/CMakeFiles/container-executor.dir/DependInfo.cmake; is newer than depender /home/jenkins/jenksrc/main/native/container-executor/impl/main.c:143:9: warning: ignoring return value of 'setuid', declared with attribute warn_uins-slave/workspace/Hadoop-Yarn-trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/nnused_result [-Wunused-result] [exec]setuid(0); [exec] ^ [exec] https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-projative/CMakeFiles/container-executor.dir/depend.internal;. [exec] Dependee https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoect/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/main.c:145:9: warning:op-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/native/CMakeFiles/CMakeDirectoryInformation ignoring return value of 'setgid', declared with attribute warn_unused_result [-Wunused-result] [exec]setgid(group_info-gr_gid); [exec] .cmake is newer than depender https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-y ^ [exec] arn-server/hadoop-yarn-server-nodemanager/target/native/CMakeFiles/container-executor.dir/depend.internal. [exec] Scanning dependencies of target container-executor [exec] make[2]: Leaving directory `https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/native' [exec] make -f CMakeFiles/container-executor.dir/build.make CMakeFiles/container-executor.dir/build [exec] make[2]: Entering directory `https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/native' [exec] /usr/bin/cmake -E cmake_progress_report https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/native/CMakeFiles 3 [exec] [ 75%] Building C object CMakeFiles/container-executor.dir/main/native/container-executor/impl/main.c.o [exec] /usr/bin/cc -g -Wall -O2 -D_GNU_SOURCE -D_REENTRANT -Ihttps://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src -Ihttps://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/native -Ihttps://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor -Ihttps://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl -o CMakeFiles/container-executor.dir/main/native/container-executor/impl/main.c.o -c https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/native/container-executor/impl/main.c [exec] Linking C executable target/usr/local/bin/container-executor [exec] /usr/bin/cmake -E cmake_link_script CMakeFiles/container-executor.dir/link.txt --verbose=1 [exec] /usr/bin/cc -g -Wall -O2 -D_GNU_SOURCE -D_REENTRANT CMakeFiles/container-executor.dir/main/native/container-executor/impl/main.c.o -o target/usr/local/bin/container-executor -rdynamic libcontainer.a [exec] make[2]: Leaving directory `https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/native' [exec] /usr/bin/cmake -E cmake_progress_report https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/native/CMakeFiles 3
Build failed in Jenkins: Hadoop-Yarn-trunk-Java8 #134
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/134/changes Changes: [xgong] YARN-3171. Sort by Application id, AppAttempt and ContainerID doesn't -- [...truncated 4767 lines...] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.743 sec - in org.apache.hadoop.yarn.server.resourcemanager.nodelabels.TestRMNodeLabelsManager Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.TestAMAuthorization Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.518 sec - in org.apache.hadoop.yarn.server.resourcemanager.TestAMAuthorization Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerApplicationAttempt Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.8 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerApplicationAttempt Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.TestFifoScheduler Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.106 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.TestFifoScheduler Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerUtils Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.081 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestSchedulerUtils Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestResourceUsage Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.475 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestResourceUsage Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestAbstractYarnScheduler Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.766 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestAbstractYarnScheduler Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestChildQueueOrder Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.985 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestChildQueueOrder Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestLeafQueue Tests run: 24, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.981 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestLeafQueue Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestQueueMappings Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.23 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestQueueMappings Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerQueueACLs Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 53.843 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerQueueACLs Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 239.952 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestApplicationLimits Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.2 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestApplicationLimits Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler Tests run: 37, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 111.571 sec - in
Failed: YARN-3273 PreCommit Build #6973
Jira: https://issues.apache.org/jira/browse/YARN-3273
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6973/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3709 lines...]
http://issues.apache.org/jira/secure/attachment/12704785/0002-YARN-3273.patch
against trunk revision 3da9a97.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestNodesPage
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6973//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6973//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6973//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
8f2db918e9b9a655a2d3a6d2e9a318a5df19f07f logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6957
Archived 20 artifacts
Archive block size is 32768
Received 43 blocks and 7798074 bytes
Compression is 15.3%
Took 2.3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
7 tests failed.
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler.testBlackListNodes
Error Message:
null
Stack Trace:
java.lang.NullPointerException: null
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt.setApplicationHeadroomForMetrics(SchedulerApplicationAttempt.java:637)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.FifoScheduler.allocate(FifoScheduler.java:347)
at
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler.testBlackListNodes(TestFifoScheduler.java:396)
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler.testHeadroom
Error Message:
null
Stack Trace:
java.lang.NullPointerException: null
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerApplicationAttempt.setApplicationHeadroomForMetrics(SchedulerApplicationAttempt.java:637)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.FifoScheduler.allocate(FifoScheduler.java:347)
at
org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler.testHeadroom(TestFifoScheduler.java:497)
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestNodesPage.testNodesBlockRenderForNodeLabelFilterWithEmptyLabel
Error Message:
printWriter.print(td);
Wanted 146 times:
- at
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestNodesPage.testNodesBlockRenderForNodeLabelFilterWithEmptyLabel(TestNodesPage.java:133)
But was 150 times. Undesired invocation:
- at
org.apache.hadoop.yarn.webapp.hamlet.HamletImpl.printStartTag(HamletImpl.java:273)
Stack Trace:
org.mockito.exceptions.verification.TooManyActualInvocations:
printWriter.print(td);
Wanted 146 times:
- at
Failed: YARN-3212 PreCommit Build #6974
Jira: https://issues.apache.org/jira/browse/YARN-3212
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6974/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3499 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704811/YARN-3212-v2.patch
against trunk revision d1eebd9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6974//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6974//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6974//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
33a5dc17f21ee608da8ea818e84ec5be0a434beb logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6957
Archived 20 artifacts
Archive block size is 32768
Received 45 blocks and 7975120 bytes
Compression is 15.6%
Took 3.8 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-3357) Move TestFifoScheduler to FIFO package
Rohith created YARN-3357: Summary: Move TestFifoScheduler to FIFO package Key: YARN-3357 URL: https://issues.apache.org/jira/browse/YARN-3357 Project: Hadoop YARN Issue Type: Task Components: scheduler Reporter: Rohith Assignee: Rohith There are 2 test classes are found for fifo scheduler i.e # org.apache.hadoop.yarn.server.resourcemanager.TestFifoScheduler # org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo.TestFifoScheduler. In these some test cases are common in both that does same functionality has been verified i.e testBlackListNodes. Tests from package org.apache.hadoop.yarn.server.resourcemanager can be merged with package org.apache.hadoop.yarn.server.resourcemanager.scheduler.fifo. And eliminate duplicate tests -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Hadoop - Major releases
I took the liberty of adding line breaks to Joep's mail. Thanks for the great feedback Joep. The goal with 3.x is to maintain API and wire compatibility with 2.x, which I think addresses most of your concerns. A 2.x client running on JDK7 would then still be able to talk to a 3.x server running on JDK8. Classpath isolation is also proposed as a banner feature, which directly addresses g). This might require new (major?) releases for some downstreams, but the feedback I've heard related to this has been very positive. Best, Andrew == It depends on the Return on Pain. While it is hard to quantify the returns in the abstract, I can try to sketch out which kinds of changes are the most painful and therefore cause the most friction for us.In rough order of increasing pain to deal with: a) There is a new upstream (3.x) release, but it is so backwards incompatible, that we won't be able to adopt it for the foreseeable future. Even though we don’t adopt it, it still causes pain. Now development becomes that much harder because we'd have to get a patch for trunk, a patch for 3.x and a patch for the 2.x branch. Conversely if patches go into 2.x only, now the releases start drifting apart. We already have (several dozen) patches in production that have not yet made it upstream, but are striving to keep this list as short as possible to reduce the rebase pain and risk. b) Central Daemons (RM, or pairs of HA NNs) have to be restarted causing a cluster-wide outage. The work towards work-preserving restart in progress in various areas makes these kinds of upgrades less painful. c) Server-side requires different runtime from client-side. We'd have to produce multiple artifacts, but we could make that work. For example, NN code uses Java 8 features, but clients can still use Java 7 to submit jobs and read/write HDFS. Now for the more painful backwards incompatibilities: d) All clients have to recompile (a token uses protobuf instead of thrift, an interface becomes an abstract class or vice versa). Not only do these kinds of changes make a rolling upgrade impossible, more importantly it requires all our clients to recompile their code and redeploy their production pipelines in a coordinated fashion. On top of this, we have multiple large production clusters and clients would have to keep multiple incompatible pipelines running, because we simply cannot upgrade all clusters in all datacenters at the same time. e) Customers are forced to restart and can no longer run with JDK 7 clients because job submission client code or HDFS has started using JDK 8-only features. Eventually group will reduce, but for at least another year if not more this will be very painful. f) Even more painful is when Yarn/MapReduce APIs change so that customers not only have to recompile, but also have to change hundreds of scripts / flows in order to deal with the API change. This problem is compounded by other tools in the Hadoop ecosystem that would have to deal with these changes. There would be two different versions of Cascading, HBase, Hive, Pig, Spark, Tez, you name it. g) Without proper classpath isolation, third party dependency changes (guava, protobuf version, etc) are probably as painful as API changes. h) HDFS client API get changed in a backwards incompatible way requiring all clients to change their code, recompile and re-start their services in a coordinated way. We have tens of thousands of production servers reading from / writing to Hadoop and cannot have all of these long running clients restart at the same time. To put these in perspective, despite us being one of the early adopters of Hadoop 2 in production at the scale of many thousands of nodes, we are still wrapping up the migration from our last Hadoop 1 clusters. We have many war stories about many of the above incompatibilities. As I've tweeted about publicly the gains have been significant with this migration to Hadoop 2, but the friction has also been considerable. To get specific about JDK 8, we are intending to move to Java 8. Right now we're letting clients choose to run tasks with JDK 8 optionally, then we'll make it default. We'll switch to the daemons running with JDK 8. What we're concerned it would then be feasible to use JDK 8 features on the servers side (see c) above). I'm suggesting that if we do allow backwards incompatible changes, we introduce an upgrade path through an agreed upon stepping stone release. For example, a protocol changing from thrift to protobuf can be done in steps. In the stepping-stone release both would be accepted. in the following release (or two releases later) the thrift version support is dropped.This would allow for a rolling upgrade, or even if a cluster-wide restart is needed, at least customers can adopt to the change at a pace of weeks or months. Once no more (important) customers are running the thrift client, we could then roll to the next release. It would be useful to coordinate the backwards
Success: YARN-3344 PreCommit Build #6984
Jira: https://issues.apache.org/jira/browse/YARN-3344
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6984/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3319 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704906/YARN-3344-branch-trunk.002.patch
against trunk revision 2681ed9.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6984//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6984//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
be08ccb104a2191e5979a6a2969d9cc021f26a80 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6981
Archived 15 artifacts
Archive block size is 32768
Received 56 blocks and 7205567 bytes
Compression is 20.3%
Took 1.6 sec
Description set: YARN-3344
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Success: YARN-3335 PreCommit Build #6981
Jira: https://issues.apache.org/jira/browse/YARN-3335
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6981/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3284 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704859/YARN-3335.2.patch
against trunk revision ce5de93.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6981//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6981//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
abbbd293b86bc28d86e0f424ea772ac202edd1e8 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6979
Archived 15 artifacts
Archive block size is 32768
Received 47 blocks and 7359875 bytes
Compression is 17.3%
Took 1.6 sec
Description set: YARN-3335
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-3354) Container should contains node-labels asked by original ResourceRequests
Wangda Tan created YARN-3354: Summary: Container should contains node-labels asked by original ResourceRequests Key: YARN-3354 URL: https://issues.apache.org/jira/browse/YARN-3354 Project: Hadoop YARN Issue Type: Sub-task Components: api, capacityscheduler, nodemanager, resourcemanager Reporter: Wangda Tan Assignee: Wangda Tan We proposed non-exclusive node labels in YARN-3214, makes non-labeled resource requests can be allocated on labeled nodes which has idle resources. To make preemption work, we need know an allocated container's original node label: when labeled resource requests comes back, we need kill non-labeled containers running on labeled nodes. This requires add node-labels in Container, and also, NM need store this information and send back to RM when RM restart to recover original container. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3353) provide RPC metrics via JMX for timeline collectors and readers
Sangjin Lee created YARN-3353: - Summary: provide RPC metrics via JMX for timeline collectors and readers Key: YARN-3353 URL: https://issues.apache.org/jira/browse/YARN-3353 Project: Hadoop YARN Issue Type: Sub-task Components: timelineserver Reporter: Sangjin Lee We should provide RPC metrics via JMX for timeline collectors and readers. One challenge we may have is it might be difficult to provide a stable view for the metrics, given the distributed nature of the collectors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3355) findbugs warning:Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.allocConf
zhihai xu created YARN-3355: --- Summary: findbugs warning:Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.allocConf Key: YARN-3355 URL: https://issues.apache.org/jira/browse/YARN-3355 Project: Hadoop YARN Issue Type: Bug Components: scheduler Reporter: zhihai xu Assignee: zhihai xu findbugs warning:Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.allocConf The findbugs warning found out two Unsynchronized access: 1. FairScheduler.getPlanQueues. It looks like we should add lock at FairScheduler.getPlanQueues. Because getPlanQueues will be called by AbstractReservationSystem.reinitialize. 2. FairScheduler.getAllocationConfiguration, which looks like ok without lock. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3356) Capacity Scheduler LeafQueue.User/FiCaSchedulerApp should use ResourceUsage to track used-resources-by-label.
Wangda Tan created YARN-3356: Summary: Capacity Scheduler LeafQueue.User/FiCaSchedulerApp should use ResourceUsage to track used-resources-by-label. Key: YARN-3356 URL: https://issues.apache.org/jira/browse/YARN-3356 Project: Hadoop YARN Issue Type: Sub-task Components: capacityscheduler, resourcemanager Reporter: Wangda Tan Assignee: Wangda Tan Simliar to YARN-3099, Capacity Scheduler's LeafQueue.User/FiCaSchedulerApp should use ResourceRequest to track resource-usage/pending by label for better resource tracking and preemption. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-3343 PreCommit Build #6971
Jira: https://issues.apache.org/jira/browse/YARN-3343
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6971/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3432 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704716/0001-YARN-3343.patch
against trunk revision 3ff1ba2.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6971//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6971//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6971//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
7acc8d71289eab05586c64778f0412035b7b7410 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6957
Archived 15 artifacts
Archive block size is 32768
Received 46 blocks and 7577326 bytes
Compression is 16.6%
Took 2.3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-3352) Change distributed shell to use TIMELINE_SERVICE_VERSION
Li Lu created YARN-3352: --- Summary: Change distributed shell to use TIMELINE_SERVICE_VERSION Key: YARN-3352 URL: https://issues.apache.org/jira/browse/YARN-3352 Project: Hadoop YARN Issue Type: Sub-task Reporter: Li Lu Assignee: Li Lu After YARN-3034, we have a new global configuration for active timeline service version. We may want to use that new setting in distributed shell, instead of a customized command-line setting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Distributed shell with host affinity and relaxLocality
Hey all, We have been testing YARN with host-specific ContainerRequests. For our tests, we've been using the DistributedShell example. We've applied YARN-1974, which allows us to specify node lists, relax locality, etc. Everything seems to work as expected when we have relaxLocality set to false, and we request a specific host. When we set relaxLocality to true, things get weird. We run three nodes: node1, node2, and node3. When we start DistributedShell with, we configure it (via CLI params) to use two containers, and have a host-level request for node3. What we observe is that the AM and one container both end up on node2, and a third container ends up on node3. There are enough resources for node3 to handle both containers, but the second one doesn't end up there. We also notice that the DistributedShell app wedges because the container on node3 never completes. What is the expected behavior here? This seems to be broken. Cheers, Chris
Failed: YARN-3197 PreCommit Build #6978
Jira: https://issues.apache.org/jira/browse/YARN-3197
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6978/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3114 lines...]
cat:
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/testrun_hadoop-yarn-common.txt:
No such file or directory
awk: cannot open
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/testrun_hadoop-yarn-common.txt
(No such file or directory)
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704829/YARN-3197.004.patch
against trunk revision ed4e72a.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6978//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6978//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
7ec402bb6a6d30efcce325b730591e7b8487a960 logged out
==
==
Finished build.
==
==
Archiving artifacts
ERROR: No artifacts found that match the file pattern patchprocess/*.*.
Configuration error?
ERROR: ?patchprocess/*.*? doesn?t match anything, but ?*.*? does. Perhaps
that?s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-3350 PreCommit Build #6977
Jira: https://issues.apache.org/jira/browse/YARN-3350
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6977/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3322 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12704841/YARN-3350.2.patch
against trunk revision ed4e72a.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6977//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6977//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
fa94926c8d41268706df7cf899e87c51cf5c7a3e logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6957
Archived 15 artifacts
Archive block size is 32768
Received 44 blocks and 7598769 bytes
Compression is 15.9%
Took 3.2 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
