Success: YARN-906 PreCommit Build #1624
Jira: https://issues.apache.org/jira/browse/YARN-906
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1624/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2934 lines...]
/bin/kill -9 24440
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595131/YARN-906.4.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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
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/1624//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1624//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
e6a7f0b832abd7609c413f05d2608cab1ec53654 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-906
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Resolved] (YARN-946) Adding HDFS implementation for Histrory Reader Interface
[ https://issues.apache.org/jira/browse/YARN-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-946. -- Resolution: Duplicate Close the ticket as we decided to create the history storage which implement reader and writer together. Thx! Adding HDFS implementation for Histrory Reader Interface Key: YARN-946 URL: https://issues.apache.org/jira/browse/YARN-946 Project: Hadoop YARN Issue Type: Sub-task Reporter: Mayank Bansal Assignee: Mayank Bansal By default we decided to do the HDFS implementation for HistoryReader Interface. Thanks, Mayank -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (YARN-1003) Add a maxContainersPerNode config to the Fair Scheduler
Sandy Ryza created YARN-1003: Summary: Add a maxContainersPerNode config to the Fair Scheduler Key: YARN-1003 URL: https://issues.apache.org/jira/browse/YARN-1003 Project: Hadoop YARN Issue Type: Improvement Components: scheduler Affects Versions: 2.1.0-beta Reporter: Sandy Ryza Assignee: Karthik Kambatla -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Jenkins build is back to normal : Hadoop-Yarn-trunk #287
See https://builds.apache.org/job/Hadoop-Yarn-trunk/287/changes
[jira] [Created] (YARN-1005) Log aggregators should check for FSDataOutputStream close before renaming to aggregated file.
Rohith Sharma K S created YARN-1005:
---
Summary: Log aggregators should check for FSDataOutputStream close
before renaming to aggregated file.
Key: YARN-1005
URL: https://issues.apache.org/jira/browse/YARN-1005
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 2.1.0-beta, 2.0.5-alpha
Reporter: Rohith Sharma K S
If AggregatedLogFormat.LogWriter.closeWriter() is interuppted, then
remoteNodeTmpLogFileForApp is renamed to remoteNodeLogFileForApp file. This
renamed file does not contain valid aggregated logs. There can be situation
renamed file can be not in BCFile format.
This cause issue while viewing from JobHistoryServer web page.
{noformat}
2013-07-27 18:51:14,787 ERROR org.apache.hadoop.yarn.webapp.View: Error getting
logs for job_1374918614757_0002
java.io.IOException: Not a valid BCFile.
at
org.apache.hadoop.io.file.tfile.BCFile$Magic.readAndVerify(BCFile.java:927)
at org.apache.hadoop.io.file.tfile.BCFile$Reader.init(BCFile.java:628)
at org.apache.hadoop.io.file.tfile.TFile$Reader.init(TFile.java:804)
at
org.apache.hadoop.yarn.logaggregation.AggregatedLogFormat$LogReader.init(AggregatedLogFormat.java:337)
at
org.apache.hadoop.yarn.webapp.log.AggregatedLogsBlock.render(AggregatedLogsBlock.java:89)
at
org.apache.hadoop.yarn.webapp.view.HtmlBlock.render(HtmlBlock.java:64)
at
org.apache.hadoop.yarn.webapp.view.HtmlBlock.renderPartial(HtmlBlock.java:74)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Release Apache Hadoop 2.1.0-beta
On 30 July 2013 14:29, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created another release candidate (rc1) for hadoop-2.1.0-beta that I would like to get released. This RC fixes a number of issues reported on the previous candidate. This release represents a *huge* amount of work done by the community (~650 fixes) which includes several major advances including: # HDFS Snapshots # Windows support # YARN API stabilization # MapReduce Binary Compatibility with hadoop-1.x # Substantial amount of integration testing with rest of projects in the ecosystem The RC is available at: http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc1/ The RC tag in svn is here: http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc1 The maven artifacts are available via repository.apache.org. I don't see them under http://repo.maven.apache.org/maven2/org/apache/hadoop/hadoop-common/hadoop-2.1.0-beta-rc1/ Is there somewhere we could serve up the Jar and Pom files before they are committed to the main repo? If you could send me the tarball of the JARs poms I could do it locally
Re: [VOTE] Release Apache Hadoop 2.1.0-beta
Steve, The artifacts should be in the staging repo: https://repository.apache.org/content/groups/staging/ If not, download source tar, expand and run mvn install -DskipTests that will build/install the JARs in the local maven cache. Thanks. On Wed, Jul 31, 2013 at 8:51 AM, Steve Loughran ste...@hortonworks.comwrote: On 30 July 2013 14:29, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created another release candidate (rc1) for hadoop-2.1.0-beta that I would like to get released. This RC fixes a number of issues reported on the previous candidate. This release represents a *huge* amount of work done by the community (~650 fixes) which includes several major advances including: # HDFS Snapshots # Windows support # YARN API stabilization # MapReduce Binary Compatibility with hadoop-1.x # Substantial amount of integration testing with rest of projects in the ecosystem The RC is available at: http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc1/ The RC tag in svn is here: http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc1 The maven artifacts are available via repository.apache.org. I don't see them under http://repo.maven.apache.org/maven2/org/apache/hadoop/hadoop-common/hadoop-2.1.0-beta-rc1/ Is there somewhere we could serve up the Jar and Pom files before they are committed to the main repo? If you could send me the tarball of the JARs poms I could do it locally -- Alejandro
RE: [VOTE] Release Apache Hadoop 2.1.0-beta
+1. Using it locally for Tez. Bikas -Original Message- From: Arun C Murthy [mailto:a...@hortonworks.com] Sent: Tuesday, July 30, 2013 6:30 AM To: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org; yarn-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org Subject: [VOTE] Release Apache Hadoop 2.1.0-beta Folks, I've created another release candidate (rc1) for hadoop-2.1.0-beta that I would like to get released. This RC fixes a number of issues reported on the previous candidate. This release represents a *huge* amount of work done by the community (~650 fixes) which includes several major advances including: # HDFS Snapshots # Windows support # YARN API stabilization # MapReduce Binary Compatibility with hadoop-1.x # Substantial amount of integration testing with rest of projects in the ecosystem The RC is available at: http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc1/ The RC tag in svn is here: http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc1 The maven artifacts are available via repository.apache.org. Please try the release and vote; the vote will run for the usual 7 days. thanks, Arun -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/
World Cloud Computing Conference Expo 2013 in Beijing
Dear Mr/Miss, World Cloud Computing Conference and exhibition 2013 jointly organized by the HNZ Media and the ictchina.net intends to be held from 27 to 28 November 2013 in Beijing Exhibition Center. With ‘big data, broadband and industry demonstration application pushing cloud practice’ as the theme, the conference starts from cloud computing construction and applications. Nearly 2500 representatives including IC designers, software developers, system integrators, units about information security, data center construction and operation companies, telecom operators, the relevant government departments and associations, medical institutions, education study institutions, internet company, banks and financial organizations, insurance and investment companies, manufacturing industry, and industries involved in energy will attend the conference for free. Profile : Grand scale: more than 2500 representatives who attend can get conference brochure, CD and post-meeting reports for free. Professional high-level: authoritative experts and scholars, business representatives, nearly 100 noted academicians in cloud computing sit and prattle about the general principle. World-wide vision:experts and manufacturers in cloud computing from the United States, the European Union, South Korea, Japan and other countries will be assembled to exchange, and delegations from Taiwan and Hong Kong are unprecedentedly invited. Delegations from cloud computing demonstration cities like Beijing, Shanghai, Shenzhen, Hangzhou and Wuxi will also interflow with the typical user groups at the convention. Luxuriant content: more than 70 lectures, 14 sessions and multi-form interaction platform comprehensively and systematically reflect the latest cloud and R D practices in depth. Remarkable application: the discussion is launched around cloud computing platform and application solutions, covering the practical application of multiple industries including internet, traffic, power grid, medical treatment and education, with an exhibition area to intuitively experience cloud computing. 14 Sessions: Key technology Cloud security solutions Cloud computing and investment and financing Cloud computing and financial informatization Cloud computing and enterprise applications and large data Cloud computing and medical informatization Cloud computing and educational informationization E-government practice of cloud Small and medium-sized enterprise cloud computing Cloud computing and the mobile Internet business development Typical case share of Cloud App Cloud and mobile terminal development Industry application and innovation Cloud computing platform and application practice More information about the conference Sponsorship prospectus for more information Who to attend: related integrated circuit design, software development, system integration, information security, data center construction and operation department, Telecommunications companies, government agencies, medical and public undertakings, career education scientific research, websites, finance, insurance and investment companies, manufacturing, energy, power, petrochemical, tobacco, railways, aviation, logistics, business services, Radio and television media, real estate, construction, transportation, pharmaceutical or chemical industry, healthcare , distributor Best regards -- lizzy zhang World Cloud Computing Conference Expo 2013 Mobile:15155181290 Email: lizzy.zh...@hnzmedia.com @hnzmedia.com Tel: +86 21 6072 3305 HNZ Media Group Adress: No.355 Molin Road, Shanghai Railway Building Tel: +86 21 60723305 | Email: wenyuan@hnzmedia.com
Success: YARN-643 PreCommit Build #1626
Jira: https://issues.apache.org/jira/browse/YARN-643
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1626/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2896 lines...]
{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 1.3.9) 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1626//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1626//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
4a7b2ac156acfcb45f582910eb9cdc3e38e4fedd logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-643
Recording test results
ln builds/lastSuccessfulBuild
/home/hudson/hudson/jobs/PreCommit-YARN-Build/lastSuccessful failed
java.nio.file.FileAlreadyExistsException:
/home/hudson/hudson/jobs/PreCommit-YARN-Build/lastSuccessful
at
sun.nio.fs.UnixException.translateToIOException(UnixException.java:88)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at
sun.nio.fs.UnixFileSystemProvider.createSymbolicLink(UnixFileSystemProvider.java:455)
at java.nio.file.Files.createSymbolicLink(Files.java:994)
at sun.reflect.GeneratedMethodAccessor342.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at hudson.Util.createSymlinkJava7(Util.java:1113)
at hudson.Util.createSymlink(Util.java:1035)
at hudson.model.AbstractBuild.createSymlink(AbstractBuild.java:494)
at hudson.model.AbstractBuild.access$700(AbstractBuild.java:105)
at
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:728)
at hudson.model.Run.execute(Run.java:1618)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:247)
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Re: [VOTE] Release Apache Hadoop 2.1.0-beta
+1 (binding) Verified the signatures. On a single node setup (non-secure), ran some HDFS commands such copy files, list files, cat etc. Ran tests such as TestDFSIO, nnbench, and testfilesystem. Verified namenode webUI. Regards, Suresh On Tue, Jul 30, 2013 at 6:29 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, I've created another release candidate (rc1) for hadoop-2.1.0-beta that I would like to get released. This RC fixes a number of issues reported on the previous candidate. This release represents a *huge* amount of work done by the community (~650 fixes) which includes several major advances including: # HDFS Snapshots # Windows support # YARN API stabilization # MapReduce Binary Compatibility with hadoop-1.x # Substantial amount of integration testing with rest of projects in the ecosystem The RC is available at: http://people.apache.org/~acmurthy/hadoop-2.1.0-beta-rc1/ The RC tag in svn is here: http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.0-beta-rc1 The maven artifacts are available via repository.apache.org. Please try the release and vote; the vote will run for the usual 7 days. thanks, Arun -- Arun C. Murthy Hortonworks Inc. http://hortonworks.com/ -- http://hortonworks.com/download/
Success: YARN-758 PreCommit Build #1627
Jira: https://issues.apache.org/jira/browse/YARN-758
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1627/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2781 lines...]
/bin/kill -9 29212
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595260/yarn-758-1.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1627//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1627//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
e7529262d363f1b4879b87dda4e4634c23ca3e27 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-758
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Success: YARN-957 PreCommit Build #1628
Jira: https://issues.apache.org/jira/browse/YARN-957
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1628/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2790 lines...]
/bin/kill -9 19144
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595262/YARN-957-20130731.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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}. The javadoc tool did not generate any
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 1.3.9) 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1628//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1628//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
f9f0e10b42c31deada4bb93af5437fecd334f4c9 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-957
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-1006) Nodes list web page on the RM web UI is broken
Jian He created YARN-1006: - Summary: Nodes list web page on the RM web UI is broken Key: YARN-1006 URL: https://issues.apache.org/jira/browse/YARN-1006 Project: Hadoop YARN Issue Type: Bug Reporter: Jian He Assignee: Jian He The nodes web page which list all the connected nodes of the cluster is broken. 1. The page is not showing in correct format/style. 2. If we restart the NM, the node list is not refreshed, but just add the new started NM to the list. The old NMs information still remain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Failed: YARN-903 PreCommit Build #1630
Jira: https://issues.apache.org/jira/browse/YARN-903
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1630/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 9 lines...]
no change for http://svn.apache.org/repos/asf/hadoop/nightly since the previous
build
No emails were triggered.
[PreCommit-YARN-Build] $ /bin/bash /tmp/hudson8492686699549531494.sh
32768
Running in Jenkins mode
==
==
Testing patch for YARN-903.
==
==
At revision 1509049.
YARN-903 patch is being downloaded at Wed Jul 31 22:51:33 UTC 2013 from
http://issues.apache.org/jira/secure/attachment/12595291/YARN-903-20130731.1.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/12595291/YARN-903-20130731.1.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1630//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
cf521ea90a229beb2f37721cb354a81a46b20641 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
Success: YARN-808 PreCommit Build #1629
Jira: https://issues.apache.org/jira/browse/YARN-808
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1629/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3583 lines...]
/bin/kill -9 30962
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595279/YARN-808.1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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}. The javadoc tool did not generate any
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 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1629//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1629//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
ccca90f232845fe1bcb1eebbbebb3f4e487b6cc1 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-808
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-573 PreCommit Build #1631
Jira: https://issues.apache.org/jira/browse/YARN-573
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1631/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2853 lines...]
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595310/YARN-573-20130731.1.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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/1631//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1631//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
a999a7566ffb67e9e6e6b4deacfab1bfff55fc58 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)
##
All tests passed
[jira] [Resolved] (YARN-770) NPE NodeStatusUpdaterImpl
[
https://issues.apache.org/jira/browse/YARN-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved YARN-770.
--
Resolution: Invalid
[~ste...@apache.org], I am closing this as invalid for now. The code has
changed a lot and it isn't apparent what was causing it.
Please feel free to reopen it when you run into it again. Thanks!
NPE NodeStatusUpdaterImpl
-
Key: YARN-770
URL: https://issues.apache.org/jira/browse/YARN-770
Project: Hadoop YARN
Issue Type: Bug
Components: nodemanager
Affects Versions: 3.0.0
Reporter: Steve Loughran
Priority: Minor
A mini yarn cluster based test just failed -NPE in the logs in
{{NodeStatusUpdaterImpl}}, which is probably a symptom of the problem, not
the cause -network trouble more likely there- but it shows there's some extra
checking for null responses.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Success: YARN-758 PreCommit Build #1633
Jira: https://issues.apache.org/jira/browse/YARN-758
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1633/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2777 lines...]
/bin/kill -9 4662
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595317/yarn-758-2.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1633//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1633//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
b22db3137770a06e874afd142fd480c8a9617a5f logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-758
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Success: YARN-107 PreCommit Build #1634
Jira: https://issues.apache.org/jira/browse/YARN-107
Build: https://builds.apache.org/job/PreCommit-YARN-Build/1634/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2870 lines...]
/bin/kill -9 25602
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595345/YARN-107.4.patch
against trunk revision .
{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}. The javadoc tool did not generate any
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 1.3.9) 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
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/1634//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1634//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
6c961deeff375f39e28c095962b1639d137180ac logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-107
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
