Failed: YARN-3131 PreCommit Build #6712
Jira: https://issues.apache.org/jira/browse/YARN-3131
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6712/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3236 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700573/yarn_3131_v5.patch
against trunk revision 9a37247.
{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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:
org.apache.hadoop.yarn.client.api.impl.TestYarnClient
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6712//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6712//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
2bf897967e33a48783ee2eabbf6920b3bcc9f0d9 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6706
Archived 15 artifacts
Archive block size is 32768
Received 185 blocks and 2734623 bytes
Compression is 68.9%
Took 1 sec
Description set: MAPREDUCE-2815
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.client.api.impl.TestYarnClient.testSubmitIncorrectQueue
Error Message:
Failed to submit application_1424811992247_0001to YARN : Application
application_1424811992247_0001 submitted by user jenkins to unknown queue:
nonexist
Stack Trace:
org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
application_1424811992247_0001to YARN : Application
application_1424811992247_0001 submitted by user jenkins to unknown queue:
nonexist
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(YarnClientImpl.java:270)
at
org.apache.hadoop.yarn.client.api.impl.TestYarnClient.testSubmitIncorrectQueue(TestYarnClient.java:239)
Re: Why return NULL_ASSIGNMENT when one app can not assign to this leaf queue?
I'm not very sure, since it's more like a hack to me, so you can just try it :). Regards, Wangda On Mon, Feb 23, 2015 at 5:22 PM, 杨逸帆Steven me@legato.ninja wrote: Hi Da, Thanks for your explain. Now I understand it better. As for the reservation, can I simply comment out the function 'reserve' in LeafQueue for capacity scheduler? Sincerely, Steven On Tue, Feb 24, 2015 at 4:57 AM, Wangda Tan wheele...@gmail.com wrote: Hi Steven, For now, CapacityScheduler trying to solve is large batch job, it allocates resource in FIFO manner, and adding capacity limits, etc. So if a job submit later cannot get resource before previous job get satisfied. This is to make big batch job can get resource quickly and finish quickly. I don't think there's a way to disable reservation. HTH, Wangda On Mon, Feb 23, 2015 at 3:37 AM, 杨逸帆Steven me@legato.ninja wrote: HI, I am learning Yarn source code, and have this confussion. In the assigncontain...@leafqueue.java, yarn will iterate all active applications and try to do the schedule work. however, I notive if one application's require is over queue limit, the function will return but not break. Say I have app#2 needs 500mb, and next app# needs 300mb. The queue now has only 400mb available left, so when app#2 canAssignToThisQueue fails, function return and leaves app#3 without schedule. And in this case, app#3 is able to run. So, what is the reason to Return here? Thank you. P.S can I disable reservation? and how to do that? Sincerely, Steven
Failed: YARN-3231 PreCommit Build #6711
Jira: https://issues.apache.org/jira/browse/YARN-3231
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6711/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3455 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700551/YARN-3231.v1.patch
against trunk revision 73bcfa9.
{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: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.scheduler.fair.TestFairScheduler
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6711//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6711//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6711//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
b1caee33b4d08dd782ae6fc4ed533e74816f18f3 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6706
Archived 15 artifacts
Archive block size is 32768
Received 35 blocks and 7923308 bytes
Compression is 12.6%
Took 1.9 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.server.resourcemanager.scheduler.fair.TestFairScheduler.testIncreaseQueueMaxRunningAppsOnTheFly
Error Message:
null
Stack Trace:
java.lang.NullPointerException: null
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.updateRootQueueMetrics(FairScheduler.java:1120)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.addNode(FairScheduler.java:835)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.handle(FairScheduler.java:1154)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler.testIncreaseQueueMaxRunningAppsOnTheFly(TestFairScheduler.java:2315)
[jira] [Created] (YARN-3248) Display count of nodes blacklisted by apps in the web UI
Varun Vasudev created YARN-3248: --- Summary: Display count of nodes blacklisted by apps in the web UI Key: YARN-3248 URL: https://issues.apache.org/jira/browse/YARN-3248 Project: Hadoop YARN Issue Type: Improvement Components: resourcemanager Reporter: Varun Vasudev Assignee: Varun Vasudev It would be really useful when debugging app performance and failure issues to get a count of the nodes blacklisted by individual apps displayed in the web UI. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-3247 PreCommit Build #6707
Jira: https://issues.apache.org/jira/browse/YARN-3247
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6707/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3433 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700368/YARN-3247.000.patch
against trunk revision b610c68.
{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/6707//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6707//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6707//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
b905f51328f41d5cc0e6629bb37446ac6ac970be logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6706
Archived 15 artifacts
Archive block size is 32768
Received 52 blocks and 7366397 bytes
Compression is 18.8%
Took 1.7 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
Hadoop-Yarn-trunk-Java8 - Build # 114 - Still Failing
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/114/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 4966 lines...] TestClientRMService.testGetClusterNodes:200 » YarnRuntime java.net.BindExcepti... Tests run: 1023, Failures: 1, Errors: 1, Skipped: 1 [INFO] [INFO] Reactor Summary: [INFO] [INFO] hadoop-yarn ... SUCCESS [ 3.213 s] [INFO] hadoop-yarn-api ... SUCCESS [01:00 min] [INFO] hadoop-yarn-common SUCCESS [02:08 min] [INFO] hadoop-yarn-server SUCCESS [ 0.060 s] [INFO] hadoop-yarn-server-common . SUCCESS [ 35.377 s] [INFO] hadoop-yarn-server-nodemanager SUCCESS [05:54 min] [INFO] hadoop-yarn-server-web-proxy .. SUCCESS [ 14.294 s] [INFO] hadoop-yarn-server-applicationhistoryservice .. SUCCESS [02:50 min] [INFO] hadoop-yarn-server-resourcemanager FAILURE [46:54 min] [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: 59:42 min [INFO] Finished at: 2015-02-24T11:31:56+00:00 [INFO] Final Memory: 77M/1040M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project hadoop-yarn-server-resourcemanager: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk-Java8/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/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-resourcemanager Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Updating HADOOP-11625 Updating HADOOP-10478 Updating HADOOP-11619 Updating YARN-2797 Updating HDFS-7807 Updating HADOOP-8642 Updating HDFS-7009 Updating HDFS-7805 Sending e-mails to: yarn-dev@hadoop.apache.org Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 2 tests failed. FAILED: org.apache.hadoop.yarn.server.resourcemanager.TestClientRMService.testGetLabelsToNodes Error Message: null Stack Trace: java.lang.AssertionError: null at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at org.apache.hadoop.yarn.server.resourcemanager.TestClientRMService.testGetLabelsToNodes(TestClientRMService.java:1492) FAILED: org.apache.hadoop.yarn.server.resourcemanager.TestClientRMService.testGetClusterNodes Error Message: java.net.BindException: Problem binding to [0.0.0.0:8032] java.net.BindException: Address already in use; For more details see: http://wiki.apache.org/hadoop/BindException Stack Trace: org.apache.hadoop.yarn.exceptions.YarnRuntimeException: java.net.BindException: Problem binding to [0.0.0.0:8032] java.net.BindException: Address already in use; For more details see: http://wiki.apache.org/hadoop/BindException at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:414) at sun.nio.ch.Net.bind(Net.java:406) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
Jenkins build is back to normal : Hadoop-Yarn-trunk #848
See https://builds.apache.org/job/Hadoop-Yarn-trunk/848/changes
Build failed in Jenkins: Hadoop-Yarn-trunk-Java8 #114
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/114/changes Changes: [cnauroth] HDFS-7009. Active NN and standby NN have different live nodes. Contributed by Ming Ma. [wheat9] HADOOP-10478. Fix new findbugs warnings in hadoop-maven-plugins. Contributed by Li Lu. [aw] HADOOP-11625. Minor fixes to command manual SLA doc (aw) [aajisaka] HADOOP-8642. Document that io.native.lib.available only controls native bz2 and zlib compression codecs. (aajisaka) [cmccabe] HDFS-7807. libhdfs htable.c: fix htable resizing, add unit test (cmccabe) [cmccabe] HDFS-7805. NameNode recovery prompt should be printed on console (Surendra Singh Lilhore via Colin P. McCabe) [gera] HADOOP-11619. FTPFileSystem should override getDefaultPort. (Brahma Reddy Battula via gera) [devaraj] YARN-2797. Add -help to yarn logs and nodes CLI command. Contributed by -- [...truncated 4773 lines...] Tests run: 82, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.864 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler 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.fair.TestAllocationFileLoaderService Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.697 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestAllocationFileLoaderService 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.fair.TestMaxRunningAppsEnforcer Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.159 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestMaxRunningAppsEnforcer 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.fair.TestFairSchedulerQueueACLs Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 53.791 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerQueueACLs 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.fair.TestQueuePlacementPolicy Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.625 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestQueuePlacementPolicy 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.fair.TestFairSchedulerConfiguration Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.433 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerConfiguration 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.fair.TestFairSchedulerFairShare Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.846 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerFairShare 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.fair.TestSchedulingPolicy Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.569 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestSchedulingPolicy 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.fair.TestFSAppAttempt Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.771 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFSAppAttempt 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.fair.TestQueueManager Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.963 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestQueueManager 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.fair.TestFSLeafQueue Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.144 sec - in org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFSLeafQueue 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.fair.TestFairSchedulerPreemption Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time
[jira] [Created] (YARN-3250) Support admin cli interface in Application Priority Manager (server side)
Sunil G created YARN-3250: - Summary: Support admin cli interface in Application Priority Manager (server side) Key: YARN-3250 URL: https://issues.apache.org/jira/browse/YARN-3250 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager Reporter: Sunil G Assignee: Sunil G Current Application Priority Manager supports only configuration via file. To support runtime configurations for admin cli and REST, a common management interface has to be added which can be shared with NodeLabelsManager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity
Jason Lowe created YARN-3251: Summary: CapacityScheduler deadlock when computing absolute max avail capacity Key: YARN-3251 URL: https://issues.apache.org/jira/browse/YARN-3251 Project: Hadoop YARN Issue Type: Bug Affects Versions: 2.6.0 Reporter: Jason Lowe Priority: Blocker The ResourceManager can deadlock in the CapacityScheduler when computing the absolute max available capacity for user limits and headroom. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3252) YARN LinuxContainerExecutor runs as nobody in Simple Security mode for all applications
Eric Yang created YARN-3252: --- Summary: YARN LinuxContainerExecutor runs as nobody in Simple Security mode for all applications Key: YARN-3252 URL: https://issues.apache.org/jira/browse/YARN-3252 Project: Hadoop YARN Issue Type: Bug Affects Versions: 2.5.2, 2.5.1, 2.6.0, 2.4.0, 2.3.0 Environment: Linux Reporter: Eric Yang Priority: Critical When using YARN + Slider + LinuxContainerExecutor, all slider application are running as nobody. This is because the modification in YARN-1253 to restrict all containers to run as a single user. This becomes a exploite to any application that runs inside YARN + Slider + LCE. The original behavior is more correct. The original statement indicated that users can impersonate any other users. This supposed to be only valid for proxy users, who can proxy as other users. It is designed as intended that the service user needs to be trusted by the framework to impersonate end users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-3080 PreCommit Build #6710
Jira: https://issues.apache.org/jira/browse/YARN-3080
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6710/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3507 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700542/YARN-3080.patch
against trunk revision 73bcfa9.
{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 7 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-nodemanager:
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6710//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6710//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-nodemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6710//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
4ea29f8638ff69c6f151880c2b1207b239609b71 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6706
Archived 15 artifacts
Archive block size is 32768
Received 189 blocks and 2801015 bytes
Compression is 68.9%
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)
##
1 tests failed.
FAILED:
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService.testFailedDirsResourceRelease
Error Message:
Argument(s) are different! Wanted:
eventHandler.handle(
custom argument matcher
);
- at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService.testFailedDirsResourceRelease(TestResourceLocalizationService.java:2295)
Actual invocation has different arguments:
eventHandler.handle(
EventType: APPLICATION_INITED
);
- at
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
Stack Trace:
org.mockito.exceptions.verification.junit.ArgumentsAreDifferent:
Argument(s) are different! Wanted:
eventHandler.handle(
custom argument matcher
);
- at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService.testFailedDirsResourceRelease(TestResourceLocalizationService.java:2295)
Actual invocation has different arguments:
eventHandler.handle(
EventType: APPLICATION_INITED
);
- at
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:175)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestResourceLocalizationService.testFailedDirsResourceRelease(TestResourceLocalizationService.java:2295)
Failed: YARN-3249 PreCommit Build #6724
Jira: https://issues.apache.org/jira/browse/YARN-3249
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6724/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3522 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700684/YARN-3249.2.patch
against trunk revision 6cbd9f1.
{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: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/6724//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6724//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6724//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
d5e37f549d32c289ba2418336a2fda1d4b5d9d51 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6713
Archived 20 artifacts
Archive block size is 32768
Received 42 blocks and 8057733 bytes
Compression is 14.6%
Took 1.9 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-3249 PreCommit Build #6722
Jira: https://issues.apache.org/jira/browse/YARN-3249
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6722/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 26 lines...]
Testing patch for YARN-3249.
==
==
HEAD is now at 6cbd9f1 YARN-3247. TestQueueMappings should use
CapacityScheduler explicitly. Contributed by Zhihai Xu.
Previous HEAD position was 6cbd9f1... YARN-3247. TestQueueMappings should use
CapacityScheduler explicitly. Contributed by Zhihai Xu.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 2 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 6cbd9f1113fca9ff86fd6ffa783ecd54b147e0db.
YARN-3249 patch is being downloaded at Wed Feb 25 05:40:27 UTC 2015 from
http://issues.apache.org/jira/secure/attachment/12700677/screenshot.png
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
patch: Only garbage was found in the patch input.
patch: Only garbage was found in the patch input.
patch: Only garbage was found in the patch input.
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/12700677/screenshot.png
against trunk revision 6cbd9f1.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6722//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
a46503d7be46287529eb161eb639b22e20739ecc 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.
[jira] [Created] (YARN-3255) RM and NM main() should support generic options
Konstantin Shvachko created YARN-3255:
-
Summary: RM and NM main() should support generic options
Key: YARN-3255
URL: https://issues.apache.org/jira/browse/YARN-3255
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager, resourcemanager
Affects Versions: 2.5.0
Reporter: Konstantin Shvachko
Currently {{ResourceManager.main()}} and {{NodeManager.main()}} ignore generic
options, like {{-conf}} and {{-fs}}. It would be good to have the ability to
pass generic options in order to specify configuration files or the NameNode
location, when the services start through {{main()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Failed: YARN-1809 PreCommit Build #6723
Jira: https://issues.apache.org/jira/browse/YARN-1809
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6723/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3861 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700680/YARN-1809.11.patch
against trunk revision 6cbd9f1.
{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-api
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-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebAppFairScheduler
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6723//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6723//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6723//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
7bb791528a2bf4738c649514ea1a1254c525387c logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6713
Archived 30 artifacts
Archive block size is 32768
Received 50 blocks and 8010604 bytes
Compression is 17.0%
Took 2.1 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
2 tests failed.
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebAppFairScheduler.testFairSchedulerWebAppPageInInconsistentState
Error Message:
Failed to render FairSchedulerPage:
org.apache.hadoop.yarn.webapp.WebAppException: Error rendering block:
nestLevel=6 expected 5
at org.apache.hadoop.yarn.webapp.view.HtmlBlock.render(HtmlBlock.java:69)
at
org.apache.hadoop.yarn.webapp.view.HtmlBlock.renderPartial(HtmlBlock.java:77)
at org.apache.hadoop.yarn.webapp.View.render(View.java:235)
at
org.apache.hadoop.yarn.webapp.view.HtmlBlock$Block.subView(HtmlBlock.java:41)
at org.apache.hadoop.yarn.webapp.hamlet.Hamlet._(Hamlet.java:30347)
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.FairSchedulerPage$QueuesBlock.render(FairSchedulerPage.java:190)
at org.apache.hadoop.yarn.webapp.view.HtmlBlock.render(HtmlBlock.java:67)
at
org.apache.hadoop.yarn.webapp.view.HtmlBlock.renderPartial(HtmlBlock.java:77)
at org.apache.hadoop.yarn.webapp.View.render(View.java:235)
at org.apache.hadoop.yarn.webapp.view.HtmlPage$Page.subView(HtmlPage.java:49)
at org.apache.hadoop.yarn.webapp.hamlet.HamletImpl$EImp._v(HamletImpl.java:117)
at org.apache.hadoop.yarn.webapp.hamlet.Hamlet$TD._(Hamlet.java:845)
at
org.apache.hadoop.yarn.webapp.view.TwoColumnLayout.render(TwoColumnLayout.java:56)
at org.apache.hadoop.yarn.webapp.view.HtmlPage.render(HtmlPage.java:82)
at
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebAppFairScheduler.testFairSchedulerWebAppPageInInconsistentState(TestRMWebAppFairScheduler.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
[jira] [Created] (YARN-3254) HealthReport should include disk full information
Akira AJISAKA created YARN-3254: --- Summary: HealthReport should include disk full information Key: YARN-3254 URL: https://issues.apache.org/jira/browse/YARN-3254 Project: Hadoop YARN Issue Type: Improvement Components: nodemanager Affects Versions: 2.6.0 Reporter: Akira AJISAKA When a NodeManager's local disk get almost full, the NodeManager send a health report to ResourceManager that local/log dir is bad and the message is displayed on ResourceManager Web UI. It's difficult for users to detect why the dir is bad. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-2190 PreCommit Build #6718
Jira: https://issues.apache.org/jira/browse/YARN-2190
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6718/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 23 lines...]
==
==
Testing patch for YARN-2190.
==
==
HEAD is now at 1a625b8 HADOOP-11480. Typo in hadoop-aws/index.md uses wrong
scheme for test.fs.s3.name. Contributed by Ted Yu.
Previous HEAD position was 1a625b8... HADOOP-11480. Typo in hadoop-aws/index.md
uses wrong scheme for test.fs.s3.name. Contributed by Ted Yu.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 2 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 1a625b8158ab1cf765fbda962ba725503409d9fe.
YARN-2190 patch is being downloaded at Wed Feb 25 01:50:23 UTC 2015 from
http://issues.apache.org/jira/secure/attachment/12700646/YARN-2190.8.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/12700646/YARN-2190.8.patch
against trunk revision 1a625b8.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6718//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
2b4d51fe1049229ae159b94d3af9370161cc7426 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.
Request for access to builds.apache.org
Hi everyone, I am planning to work on HADOOP-9213 https://issues.apache.org/jira/browse/HADOOP-9213. For that we are planning to add a separate job which would run jcarder on a nightly basis and detect deadlocks. However for that I would require access to builds.apache.org. Let me know how to proceed on that and of anything else required from my side. Thanks and regards, Spandan
Success: YARN-3131 PreCommit Build #6713
Jira: https://issues.apache.org/jira/browse/YARN-3131
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6713/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3233 lines...]
{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-client.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6713//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6713//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
add05c7bce819770c324326ddcfccaf2c1c62cbb logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6706
ERROR: Failed to archive
{patchprocess/patchJavacWarnings.txt=patchprocess/patchJavacWarnings.txt,
patchprocess/trunkJavacWarnings.txt=patchprocess/trunkJavacWarnings.txt,
patchprocess/patchJavadocWarnings.txt=patchprocess/patchJavadocWarnings.txt,
patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html=patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html,
patchprocess/trunkJavadocWarnings.txt=patchprocess/trunkJavadocWarnings.txt,
patchprocess/patchReleaseAuditOutput.txt=patchprocess/patchReleaseAuditOutput.txt,
patchprocess/patchReleaseAuditWarnings.txt=patchprocess/patchReleaseAuditWarnings.txt,
patchprocess/patchFindbugsWarningshadoop-yarn-client.xml=patchprocess/patchFindbugsWarningshadoop-yarn-client.xml,
patchprocess/filteredPatchJavacWarnings.txt=patchprocess/filteredPatchJavacWarnings.txt,
patchprocess/patchEclipseOutput.txt=patchprocess/patchEclipseOutput.txt,
patchprocess/diffJavadocWarnings.txt=patchprocess/diffJavadocWarnings.txt,
patchprocess/filteredTrunkJavacWarnings.txt=patchprocess/filteredTrunkJavacWarnings.txt,
patchprocess/newPatchFindbugsWarningshadoop-yarn-client.xml=patchprocess/newPatchFindbugsWarningshadoop-yarn-client.xml,
patchprocess/testrun_hadoop-yarn-client.txt=patchprocess/testrun_hadoop-yarn-client.txt,
patchprocess/patchFindBugsOutputhadoop-yarn-client.txt=patchprocess/patchFindBugsOutputhadoop-yarn-client.txt}
due to internal error; falling back to full archiving
java.lang.IllegalStateException: checksum mismatch after transfer
(6577874794637500426 vs. 1094595238);
/x1/jenkins/jenkins-home/jobs/PreCommit-YARN-Build/builds/2015-02-24_21-40-13/archive/patchprocess/trunkJavacWarnings.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-3131
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
Failed: YARN-3249 PreCommit Build #6720
Jira: https://issues.apache.org/jira/browse/YARN-3249
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6720/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 26 lines...]
Testing patch for YARN-3249.
==
==
HEAD is now at 6cbd9f1 YARN-3247. TestQueueMappings should use
CapacityScheduler explicitly. Contributed by Zhihai Xu.
Previous HEAD position was 6cbd9f1... YARN-3247. TestQueueMappings should use
CapacityScheduler explicitly. Contributed by Zhihai Xu.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 11 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 6cbd9f1113fca9ff86fd6ffa783ecd54b147e0db.
YARN-3249 patch is being downloaded at Wed Feb 25 02:40:22 UTC 2015 from
http://issues.apache.org/jira/secure/attachment/12700467/screenshot.png
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
patch: Only garbage was found in the patch input.
patch: Only garbage was found in the patch input.
patch: Only garbage was found in the patch input.
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/12700467/screenshot.png
against trunk revision 6cbd9f1.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6720//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
d34820b5ed181b74b184f9875ab8055f19b368bc 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-3231 PreCommit Build #6716
Jira: https://issues.apache.org/jira/browse/YARN-3231
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6716/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3498 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700610/YARN-3231.v2.patch
against trunk revision 7105eba.
{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: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.webapp.TestRMWebServicesFairScheduler
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6716//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6716//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6716//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
28cfeab7f30d615270ae938c29e0afec0477f125 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6713
Archived 15 artifacts
Archive block size is 32768
Received 222 blocks and 1799182 bytes
Compression is 80.2%
Took 0.95 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
2 tests failed.
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesFairScheduler.testClusterScheduler
Error Message:
java.net.BindException: Address already in use
Stack Trace:
com.sun.jersey.test.framework.spi.container.TestContainerException:
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:444)
at sun.nio.ch.Net.bind(Net.java:436)
at
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at
org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:413)
at
org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:384)
at
org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:375)
at
org.glassfish.grizzly.http.server.NetworkListener.start(NetworkListener.java:549)
at
org.glassfish.grizzly.http.server.HttpServer.start(HttpServer.java:255)
at
com.sun.jersey.api.container.grizzly2.GrizzlyServerFactory.createHttpServer(GrizzlyServerFactory.java:326)
at
com.sun.jersey.api.container.grizzly2.GrizzlyServerFactory.createHttpServer(GrizzlyServerFactory.java:343)
at
com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.instantiateGrizzlyWebServer(GrizzlyWebTestContainerFactory.java:219)
at
com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.init(GrizzlyWebTestContainerFactory.java:129)
at
com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.init(GrizzlyWebTestContainerFactory.java:86)
at
Failed: YARN-3031 PreCommit Build #6717
Jira: https://issues.apache.org/jira/browse/YARN-3031
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6717/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3182 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700617/YARN-3031.02.patch
against trunk revision ac3468a.
{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-api.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6717//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6717//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
65bb2a8dbd24a42825494d451066e218aaeaa827 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6713
Archived 15 artifacts
Archive block size is 32768
Received 51 blocks and 7423325 bytes
Compression is 18.4%
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)
##
No tests ran.
[jira] [Created] (YARN-3253) Clean up SupressWarnings annotations from Find.java
Akira AJISAKA created YARN-3253: --- Summary: Clean up SupressWarnings annotations from Find.java Key: YARN-3253 URL: https://issues.apache.org/jira/browse/YARN-3253 Project: Hadoop YARN Issue Type: Improvement Affects Versions: 2.7.0 Reporter: Akira AJISAKA Assignee: Akira AJISAKA Priority: Minor There are some SuppressWarnings annotations in Find.java. We should fix them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-3231 PreCommit Build #6714
Jira: https://issues.apache.org/jira/browse/YARN-3231
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6714/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 38 lines...]
YARN-3231 patch is being downloaded at Tue Feb 24 22:20:22 UTC 2015 from
http://issues.apache.org/jira/secure/attachment/12700592/YARN-3231.v2.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
Checking patch
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FairScheduler.java...
Checking patch
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/MaxRunningAppsEnforcer.java...
Checking patch
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java...
==
==
Pre-build trunk to verify trunk stability and javac warnings
==
==
Compiling /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2
/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests
-DHadoopPatchProcess -Ptest-patch
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/trunkJavacWarnings.txt
21
/home/jenkins/tools/maven/latest/bin/mvn clean test javadoc:javadoc -DskipTests
-Pdocs -DHadoopPatchProcess
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/trunkJavadocWarnings.txt
21
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/dev-support/test-patch.sh:
line 306:
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/trunkJavadocWarnings.txt:
No such file or directory
Trunk javadoc compilation is broken?
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700592/YARN-3231.v2.patch
against trunk revision 9a37247.
{color:red}-1 patch{color}. Trunk compilation may be broken.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6714//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
b77048b7137b663381b5aa1700913426150f7769 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Description set: MAPREDUCE-2815
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
Failed: YARN-3249 PreCommit Build #6721
Jira: https://issues.apache.org/jira/browse/YARN-3249
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6721/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 56 lines...]
error: patch failed:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/AppsBlock.java:31
error:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/AppsBlock.java:
patch does not apply
Checking patch
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/KillAppBlock.java...
Checking patch
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/KillAppPage.java...
Checking patch
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMWebApp.java...
error: while searching for:
route(pajoin(/apps, APP_STATE), RmController.class);
route(/cluster, RmController.class, about);
route(pajoin(/app, APPLICATION_ID), RmController.class, app);
route(/scheduler, RmController.class, scheduler);
route(pajoin(/queue, QUEUE_NAME), RmController.class, queue);
}
error: patch failed:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMWebApp.java:66
error:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RMWebApp.java:
patch does not apply
Checking patch
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/RmController.java...
Hunk #1 succeeded at 54 (offset -1 lines).
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700464/YARN-3249.patch
against trunk revision 6cbd9f1.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6721//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
3b66fed6400931c6b4c8c31b48e57308e8112c9e 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-1809 PreCommit Build #6719
Jira: https://issues.apache.org/jira/browse/YARN-1809
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6719/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3946 lines...]
{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 8 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-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-resourcemanager:
org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebAppFairScheduler
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestAppPage
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6719//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6719//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6719//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6719//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
ee999638dc8ef048c9d32eb99068700af4f26f0c logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6713
Archived 30 artifacts
Archive block size is 32768
Received 46 blocks and 8157651 bytes
Compression is 15.6%
Took 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)
##
7 tests failed.
FAILED:
org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices.testSingleContainer[0]
Error Message:
JSONObject[logUrl] not found.
Stack Trace:
org.codehaus.jettison.json.JSONException: JSONObject[logUrl] not found.
at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360)
at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices.testSingleContainer(TestAHSWebServices.java:367)
FAILED:
org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices.testSingleAttempt[1]
Error Message:
expected:Forbidden but was:Internal Server Error
Stack Trace:
java.lang.AssertionError: expected:Forbidden but was:Internal Server Error
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.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices.testSingleAttempt(TestAHSWebServices.java:292)
FAILED:
org.apache.hadoop.yarn.server.applicationhistoryservice.webapp.TestAHSWebServices.testSingleContainer[1]
Error Message:
expected:Forbidden but was:Internal Server Error
Stack Trace:
java.lang.AssertionError:
Failed: YARN-3231 PreCommit Build #6715
Jira: https://issues.apache.org/jira/browse/YARN-3231
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6715/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 95 lines...]
==
==
Determining number of patched javac warnings.
==
==
/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests
-DHadoopPatchProcess -Pnative -Ptest-patch
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patchJavacWarnings.txt
21
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700597/YARN-3231.v2.patch
against trunk revision 9a37247.
{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:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6715//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
2ddf2248a48b6190acd51fb0abb171a022213712 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6713
Archived 3 artifacts
Archive block size is 32768
Received 83 blocks and 615223 bytes
Compression is 81.6%
Took 0.99 sec
Description set: MAPREDUCE-2815
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
