Failed: YARN-2922 PreCommit Build #6034
Jira: https://issues.apache.org/jira/browse/YARN-2922
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6034/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3358 lines...]
against trunk revision 8963515.
{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: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.TestContainerResourceUsage
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6034//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6034//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
bd4c3317b94293a8d8fbbff875fe142fc608d492 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6026
Archived 15 artifacts
Archive block size is 32768
Received 45 blocks and 7331612 bytes
Compression is 16.7%
Took 1.6 sec
Description set: MAPREDUCE-6177
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6033
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
3 tests failed.
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageAfterAMRestartWithMultipleContainers
Error Message:
AppAttempt state is not correct (timedout) expected:ALLOCATED but
was:SCHEDULED
Stack Trace:
java.lang.AssertionError: AppAttempt state is not correct (timedout)
expected:ALLOCATED but was:SCHEDULED
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.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:86)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:496)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAM(MockRM.java:661)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAndRegisterAM(MockRM.java:668)
at
org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.amRestartTests(TestContainerResourceUsage.java:272)
at
org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageAfterAMRestartWithMultipleContainers(TestContainerResourceUsage.java:251)
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.TestContainerResourceUsage.testUsageWithOneAttemptAndOneContainer
Error Message:
AppAttempt state is not correct (timedout) expected:ALLOCATED but
was:SCHEDULED
Stack Trace:
java.lang.AssertionError: AppAttempt state is not correct (timedout)
expected:ALLOCATED but was:SCHEDULED
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.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:86)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:496)
at
Failed: YARN-2683 PreCommit Build #6039
Jira: https://issues.apache.org/jira/browse/YARN-2683
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6039/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 100 lines...]
tomcat.version6.0.41/tomcat.version
/properties
dependencyManagement
error: patch failed: hadoop-project/pom.xml:73
error: hadoop-project/pom.xml: patch does not apply
Checking patch pom.xml...
error: while searching for:
version[3.0.2,)/version
/requireMavenVersion
requireJavaVersion
version1.6/version
/requireJavaVersion
/rules
/configuration
error: patch failed: pom.xml:124
error: pom.xml: patch does not apply
PATCH APPLICATION FAILED
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12685776/HADOOP-10530-005.patch
against trunk revision 57cb43b.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6039//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
eedb769b31f379a7b608b3f1f45e58d09b48537e 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] [Resolved] (YARN-405) Add command start-up time to environment of a container to track launch costs
[ https://issues.apache.org/jira/browse/YARN-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-405. -- Resolution: Not a Problem Add command start-up time to environment of a container to track launch costs - Key: YARN-405 URL: https://issues.apache.org/jira/browse/YARN-405 Project: Hadoop YARN Issue Type: Improvement Reporter: Hitesh Shah Assignee: Hitesh Shah Priority: Minor Labels: container Attachments: YARN-405.1.patch For applications like MapReduce, jvm launch cost has always been considered a factor in performance. Adding some basic information into the environment will allow an application to track its startup costs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-2931 PreCommit Build #6040
Jira: https://issues.apache.org/jira/browse/YARN-2931
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6040/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12685852/YARN-2931.001.patch
against trunk revision 6c5bbd7.
{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}. The applied patch generated 1219 javac
compiler warnings (more than the trunk's current 1217 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6040//testReport/
Javac warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6040//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6040//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
c0ce80a055c5ed79db82ee59e2ff1e915e2029fe logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6035
Archived 16 artifacts
Archive block size is 32768
Received 62 blocks and 6707321 bytes
Compression is 23.2%
Took 2.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
Re: Thinking ahead to hadoop-2.7
On 8 December 2014 at 19:48, Colin McCabe cmcc...@alumni.cmu.edu wrote: Are there a lot of open JDK7 issues that would require a release to straighten out? I don't think so —the 2.6 release was tested pretty aggressively on JDK7, and solely on it for Windows. Pushing out a 2.7 release would be more symbolic than of use to people there's one exception: the fix for java 8 security. I do also think there may be Java 8 test failures; these need to be identified and fixed ... which would point more to a 2.8 release for that -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[jira] [Created] (YARN-2933) Capacity Scheduler preemption policy should only consider capacity without labels temporarily
Wangda Tan created YARN-2933: Summary: Capacity Scheduler preemption policy should only consider capacity without labels temporarily Key: YARN-2933 URL: https://issues.apache.org/jira/browse/YARN-2933 Project: Hadoop YARN Issue Type: Sub-task Components: capacityscheduler Reporter: Wangda Tan Assignee: Wangda Tan Currently, we have capacity enforcement on each queue for each label in CapacityScheduler, but we don't have preemption policy to support that. YARN-2498 is targeting to support preemption respect node labels, but we have some gaps in code base, like queues/FiCaScheduler should be able to get usedResource/pendingResource, etc. by label. These items potentially need to refactor CS which we need spend some time carefully think about. For now, what immediately we can do is allow calculate ideal_allocation and preempt containers only for resources on nodes without labels, to avoid regression like: A cluster has some nodes with labels and some not, assume queueA isn't satisfied for resource without label, but for now, preemption policy may preempt resource from nodes with labels for queueA, that is not correct. Again, it is just a short-term enhancement, YARN-2498 will consider preemption respecting node-labels for Capacity Scheduler which is our final target. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Thinking ahead to hadoop-2.7
On Fri, Dec 5, 2014 at 11:15 AM, Karthik Kambatla ka...@cloudera.com wrote: It would be nice to cut the branch for the next feature release (not just Java 7) in the first week of January, so we can get the RC out by the end of the month? Yesterday, this came up in an offline discussion on ATS. Given people can run 2.6 on Java 7, is there merit to doing 2.7 with the exact same bits targeting Java 7? I am okay with going through with it, as long as it doesn't delay the next feature release. Thoughts? That's a good point. I think it's important to point out that most of our users are already on JDK7. We shouldn't think of this decision as adding support for something new, we should think about it as taking something away (JDK6 support). I think it's good that we are finally moving away from supporting JDK6, but I'm not completely sure that we need to devote a whole release to that. Are there a lot of open JDK7 issues that would require a release to straighten out? best, Colin On Wed, Dec 3, 2014 at 8:59 AM, Sangjin Lee sj...@apache.org wrote: Late January sounds fine to me. I think we should be able to wrap it up much earlier than that (hopefully). Thanks, Sangjin On Tue, Dec 2, 2014 at 5:19 PM, Arun C Murthy a...@hortonworks.com wrote: Sangjin/Karthik, How about planning on hadoop-2.8 by late Jan? Thoughts? thanks, Arun On Dec 2, 2014, at 11:09 AM, Sangjin Lee sjl...@gmail.com wrote: If 2.7 is being positioned as the JDK7-only release, then it would be good to know how 2.8 lines up in terms of timing. Our interest is landing the shared cache feature (YARN-1492)... Thanks. Sangjin On Mon, Dec 1, 2014 at 2:55 PM, Karthik Kambatla ka...@cloudera.com wrote: Thanks for starting this thread, Arun. Your proposal seems reasonable to me. I suppose we would like new features and improvements to go into 2.8 then? If yes, what time frame are we looking at for 2.8? Looking at YARN, it would be nice to get a release with shared-cache and a stable version of reservation work. I believe they are well under way and should be ready in a few weeks. Regarding 2.7 release specifics, do you plan to create a branch off of current branch-2.6 and update all issues marked fixed for 2.7 to be fixed for 2.8? Thanks Karthik On Mon, Dec 1, 2014 at 2:42 PM, Arun Murthy a...@hortonworks.com wrote: Folks, With hadoop-2.6 out it's time to think ahead. As we've discussed in the past, 2.6 was the last release which supports JDK6. I'm thinking it's best to try get 2.7 out in a few weeks (maybe by the holidays) with just the switch to JDK7 (HADOOP-10530) and possibly support for JDK-1.8 (as a runtime) via HADOOP-11090. This way we can start with the stable base of 2.6 and switch over to JDK7 to allow our downstream projects to use either for a short time (hadoop-2.6 or hadoop-2.7). I'll update the Roadmap wiki accordingly. Thoughts? thanks, Arun -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/hdp/ -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- -- Karthik Kambatla, Software Engineer, Cloudera Q: Why is this email five sentences or less? A: http://five.sentenc.es
Failed: YARN-2920 PreCommit Build #6044
Jira: https://issues.apache.org/jira/browse/YARN-2920
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6044/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3353 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 1 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 1218 javac
compiler warnings (more than the trunk's current 1217 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:red}-1 release audit{color}. The applied patch generated 2
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
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6044//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6044//artifact/patchprocess/patchReleaseAuditProblems.txt
Javac warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6044//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6044//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
b49b00b5ac45c84708d75b19c5e98187e374bd3d logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6041
Archived 17 artifacts
Archive block size is 32768
Received 219 blocks and 1106724 bytes
Compression is 86.6%
Took 0.66 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.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:960)
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:960)
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:960)
Failed: YARN-2837 PreCommit Build #6045
Jira: https://issues.apache.org/jira/browse/YARN-2837
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6045/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3407 lines...]
http://issues.apache.org/jira/secure/attachment/12685897/YARN-2837.5.patch
against trunk revision ddffcd8.
{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 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: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-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6045//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6045//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-common.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6045//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
643f4a31db26c4dbcaf8475d29fded5131c5fdae logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6041
Archived 25 artifacts
Archive block size is 32768
Received 55 blocks and 7505153 bytes
Compression is 19.4%
Took 1.7 sec
[description-setter] Could not determine description.
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6044
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-2931 PreCommit Build #6048
Jira: https://issues.apache.org/jira/browse/YARN-2931
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6048/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3330 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12685928/YARN-2931.004.patch
against trunk revision ddffcd8.
{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 2 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6048//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6048//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-nodemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6048//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
f017faec03d59d8cc49ef2428a53821cc64790d9 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6046
Archived 15 artifacts
Archive block size is 32768
Received 61 blocks and 6749193 bytes
Compression is 22.8%
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-2931 PreCommit Build #6049
Jira: https://issues.apache.org/jira/browse/YARN-2931
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6049/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3330 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12685928/YARN-2931.004.patch
against trunk revision ddffcd8.
{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 2 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6049//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6049//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-nodemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6049//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
223847179080888bf48a4fee0f790beef11e16af logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6046
Archived 15 artifacts
Archive block size is 32768
Received 54 blocks and 6978533 bytes
Compression is 20.2%
Took 1.5 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
Success: YARN-2931 PreCommit Build #6051
Jira: https://issues.apache.org/jira/browse/YARN-2931
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6051/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3329 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12685935/YARN-2931.005.patch
against trunk revision ddffcd8.
{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-server/hadoop-yarn-server-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6051//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6051//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
8de4f941d793feb59d094cd4717a153278cdf809 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6046
Archived 15 artifacts
Archive block size is 32768
Received 61 blocks and 6738429 bytes
Compression is 22.9%
Took 1.6 sec
Description set: YARN-2931
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6050
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-2930 PreCommit Build #6050
Jira: https://issues.apache.org/jira/browse/YARN-2930
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6050/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3332 lines...]
http://issues.apache.org/jira/secure/attachment/12685916/YARN-2930.1.patch
against trunk revision ddffcd8.
{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: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.security.TestRMDelegationTokens
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6050//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6050//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
4b919e35663b88635e7e679da683dc0e5105ee61 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6046
Archived 15 artifacts
Archive block size is 32768
Received 57 blocks and 6941216 bytes
Compression is 21.2%
Took 1.5 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.security.TestRMDelegationTokens.testRMDTMasterKeyStateOnRollingMasterKey
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.security.TestRMDelegationTokens$TestRMDelegationTokenSecretManager.checkCurrentKeyInStateStore(TestRMDelegationTokens.java:208)
at
org.apache.hadoop.yarn.server.resourcemanager.security.TestRMDelegationTokens.testRMDTMasterKeyStateOnRollingMasterKey(TestRMDelegationTokens.java:112)
Failed: YARN-2910 PreCommit Build #6052
Jira: https://issues.apache.org/jira/browse/YARN-2910
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6052/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3347 lines...]
against trunk revision ddffcd8.
{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 9 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
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6052//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6052//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6052//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
53cb278855071616f43164ccd53bfc8d6ac7f1a5 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6051
Archived 15 artifacts
Archive block size is 32768
Received 3 blocks and 8554409 bytes
Compression is 1.1%
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)
##
2 tests failed.
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartRecoveringNodeLabelManager[0]
Error Message:
expected:1 but was:2
Stack Trace:
java.lang.AssertionError: expected:1 but was:2
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:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartRecoveringNodeLabelManager(TestRMRestart.java:2100)
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartRecoveringNodeLabelManager[1]
Error Message:
expected:1 but was:2
Stack Trace:
java.lang.AssertionError: expected:1 but was:2
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:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartRecoveringNodeLabelManager(TestRMRestart.java:2100)
Failed: YARN-2910 PreCommit Build #6053
Jira: https://issues.apache.org/jira/browse/YARN-2910
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6053/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3027 lines...]
/bin/kill -9 5943
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12685939/YARN-2910.6.patch
against trunk revision ddffcd8.
{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 .
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6053//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6053//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
f0df8505f105a2b5f92303e449c9773249142053 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.
Re: Upgrading findbugs
Thanks for initiating this, Haohui. +1 to upgrading findbugs version. Inline. On Mon, Dec 8, 2014 at 9:57 PM, Haohui Mai h...@hortonworks.com wrote: Hi, The recent changes on moving to Java 7 triggers a bug in findbug ( http://sourceforge.net/p/findbugs/bugs/918), which causes all pre-commit runs (e.g., HADOOP-11287) to fail. The current version of findbugs (1.3.9) used by Hadoop is released in 2009. Given that: (1) The current bug that we hit are fixed by a later version of findbug. (2) A newer findbug (3.0.0) is required to analyze Hadoop that is compiled against Java 8. (3) Newer findbugs are capable of catching more bugs. :-) Is it a good time to consider upgrading findbugs, which gives us better tools on ensuring the quality of the code case? I ran findbugs 3.0.0 against trunk today. It reported 111 warnings for hadoop-common, 44 for HDFS and 40+ for YARN. Many of them are possible NPEs, resource leaks, and ignored exception which are indeed bugs and are worthwhile to address. However, one issue that needs to be considered is that how to deal with the additional warnings reported by the newer findbugs without breaking the Jenkins pre-commit runs. Personally I can see three possible routes if we decide to upgrade findbugs: (1) Fix all warnings before upgrading to newer findbugs. This might take a while. We might want to use the newer findbugs sooner? (2) Add all new warnings to the exclude list and fix them slowly. I have my doubts on how soon we fix these warnings unless we make the associated JIRAs (assuming we have one per exclude) blockers for the next release. A findbugs Fix It day would be ideal to get this done. (3) Update test-patch.sh to make sure that new code won't introduce any new findbugs warnings. Seems the best, especially if test-patch.sh shows the warnings, but doesn't -1 unless there are new findbugs warnings. This way, the contributor can choose to fix related warnings at the least. I proposed upgrading to findbugs 2.0.2 and fixing new warnings in HADOOP-10476, which could be dated backed to April, 2014. I volunteer to accelerate the effort if it is required. Thoughts? Regards, Haohui -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- Karthik Kambatla Software Engineer, Cloudera Inc. http://five.sentenc.es
