Hadoop-Mapreduce-trunk - Build # 1857 - Failure
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1857/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 35048 lines...] Tests run: 280, Failures: 1, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] hadoop-mapreduce-client ... SUCCESS [ 2.541 s] [INFO] hadoop-mapreduce-client-core .. SUCCESS [ 57.130 s] [INFO] hadoop-mapreduce-client-common SUCCESS [ 27.127 s] [INFO] hadoop-mapreduce-client-shuffle ... SUCCESS [ 4.373 s] [INFO] hadoop-mapreduce-client-app ... FAILURE [08:28 min] [INFO] hadoop-mapreduce-client-hs SKIPPED [INFO] hadoop-mapreduce-client-jobclient . SKIPPED [INFO] hadoop-mapreduce-client-hs-plugins SKIPPED [INFO] Apache Hadoop MapReduce Examples .. SKIPPED [INFO] hadoop-mapreduce .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 10:00 min [INFO] Finished at: 2014-08-08T15:20:50+00:00 [INFO] Final Memory: 31M/686M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project hadoop-mapreduce-client-app: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-trunk/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/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-mapreduce-client-app Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE Archiving artifacts Sending artifact delta relative to Hadoop-Mapreduce-trunk #1856 Archived 2 artifacts Archive block size is 32768 Received 0 blocks and 16976034 bytes Compression is 0.0% Took 17 sec Updating HDFS-6728 Updating HDFS-6772 Updating YARN-2008 Updating HADOOP-10771 Updating HADOOP-10929 Updating HDFS-6740 Updating YARN-2352 Updating HADOOP-10876 Updating MAPREDUCE-6021 Updating YARN-2288 Updating HDFS-6781 Updating HDFS-6722 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
[jira] [Created] (MAPREDUCE-6029) TestCommitterEventHandler fails in trunk
Ted Yu created MAPREDUCE-6029:
-
Summary: TestCommitterEventHandler fails in trunk
Key: MAPREDUCE-6029
URL: https://issues.apache.org/jira/browse/MAPREDUCE-6029
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Ted Yu
From https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1857/console :
{code}
Running org.apache.hadoop.mapreduce.v2.app.commit.TestCommitterEventHandler
Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.429 sec
FAILURE! - in
org.apache.hadoop.mapreduce.v2.app.commit.TestCommitterEventHandler
testFailure(org.apache.hadoop.mapreduce.v2.app.commit.TestCommitterEventHandler)
Time elapsed: 1.198 sec FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:621)
at org.junit.Assert.assertNotNull(Assert.java:631)
at
org.apache.hadoop.mapreduce.v2.app.commit.TestCommitterEventHandler.testFailure(TestCommitterEventHandler.java:314)
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (MAPREDUCE-6008) Update distcp docs to include new option that suppresses preservation of RAW.* namespace extended attributes
[ https://issues.apache.org/jira/browse/MAPREDUCE-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved MAPREDUCE-6008. Resolution: Not a Problem We took care of the docs in parent JIRA, no need for this one. Update distcp docs to include new option that suppresses preservation of RAW.* namespace extended attributes Key: MAPREDUCE-6008 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6008 Project: Hadoop Map/Reduce Issue Type: Sub-task Components: distcp Affects Versions: fs-encryption Reporter: Charles Lamb Assignee: Charles Lamb Update the docs to include this new option. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: [DISCUSS] Migrate from svn to git for source control?
Thanks Steve. Including that in the proposal. By the way, from our project bylaws (http://hadoop.apache.org/bylaws.html), I can't tell what kind of a vote this would be. On Thu, Aug 7, 2014 at 1:22 AM, Steve Loughran ste...@hortonworks.com wrote: On 6 August 2014 22:16, Karthik Kambatla ka...@cloudera.com wrote: 3. Force-push on feature-branches is allowed. Before pulling in a feature, the feature-branch should be rebased on latest trunk and the changes applied to trunk through git rebase --onto or git cherry-pick commit-range. I'd add to this process the requirement to tag any feature branch before a rebase, with some standard naming like tag_feature_JIRA-2454_2014-08-07_rebase Why? it keeps the state of the branch before the rebase in case you ever want it back again. Without the tag: lost data. Once the feature is merged in you can rm the tags, but until then they give you a log of what changes went on, and make it possible to switch back to the pre-rebase version. Without those tags you do lose history of the development. -- 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.
Re: [DISCUSS] Migrate from svn to git for source control?
funny, i'd treat it as a merge vote. On Fri, Aug 8, 2014 at 11:44 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks Steve. Including that in the proposal. By the way, from our project bylaws (http://hadoop.apache.org/bylaws.html ), I can't tell what kind of a vote this would be. On Thu, Aug 7, 2014 at 1:22 AM, Steve Loughran ste...@hortonworks.com wrote: On 6 August 2014 22:16, Karthik Kambatla ka...@cloudera.com wrote: 3. Force-push on feature-branches is allowed. Before pulling in a feature, the feature-branch should be rebased on latest trunk and the changes applied to trunk through git rebase --onto or git cherry-pick commit-range. I'd add to this process the requirement to tag any feature branch before a rebase, with some standard naming like tag_feature_JIRA-2454_2014-08-07_rebase Why? it keeps the state of the branch before the rebase in case you ever want it back again. Without the tag: lost data. Once the feature is merged in you can rm the tags, but until then they give you a log of what changes went on, and make it possible to switch back to the pre-rebase version. Without those tags you do lose history of the development. -- 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. -- Alejandro
Re: [DISCUSS] Migrate from svn to git for source control?
In the bylaws, I see this under PMC responsibilities: * Maintaining the project's shared resources, including the codebase repository, mailing lists, websites. This seems to indicate that the repo (i.e. svn or git) is managed by the PMC. Of the available PMC vote actions, the closest seems to be Adoption of New Codebase: When the codebase for an existing, released product is to be replaced with an alternative codebase. If such a vote fails to gain approval, the existing code base will continue. This also covers the creation of new sub-projects within the project Lazy 2/3 majority of PMC members This would be my recommendation for the vote, but I'll defer to more experienced PMC members. Thanks, Andrew On Fri, Aug 8, 2014 at 1:18 PM, Alejandro Abdelnur t...@cloudera.com wrote: funny, i'd treat it as a merge vote. On Fri, Aug 8, 2014 at 11:44 AM, Karthik Kambatla ka...@cloudera.com wrote: Thanks Steve. Including that in the proposal. By the way, from our project bylaws ( http://hadoop.apache.org/bylaws.html ), I can't tell what kind of a vote this would be. On Thu, Aug 7, 2014 at 1:22 AM, Steve Loughran ste...@hortonworks.com wrote: On 6 August 2014 22:16, Karthik Kambatla ka...@cloudera.com wrote: 3. Force-push on feature-branches is allowed. Before pulling in a feature, the feature-branch should be rebased on latest trunk and the changes applied to trunk through git rebase --onto or git cherry-pick commit-range. I'd add to this process the requirement to tag any feature branch before a rebase, with some standard naming like tag_feature_JIRA-2454_2014-08-07_rebase Why? it keeps the state of the branch before the rebase in case you ever want it back again. Without the tag: lost data. Once the feature is merged in you can rm the tags, but until then they give you a log of what changes went on, and make it possible to switch back to the pre-rebase version. Without those tags you do lose history of the development. -- 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. -- Alejandro
[jira] [Resolved] (MAPREDUCE-6028) java.lang.ArithmeticException: / by zero
[ https://issues.apache.org/jira/browse/MAPREDUCE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash resolved MAPREDUCE-6028. - Resolution: Invalid java.lang.ArithmeticException: / by zero Key: MAPREDUCE-6028 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6028 Project: Hadoop Map/Reduce Issue Type: Bug Affects Versions: 1.2.1 Environment: hadoop version:1.2.1 Reporter: eagle Run any sql through hive with following error message: 2014-08-07 10:22:28,061 INFO org.apache.hadoop.mapred.TaskInProgress: Error from attempt_201407251033_24476_m_02_0: Error initializing attempt_201407251033_24476_m_02_0: java.lang.ArithmeticException: / by zero and after restart hadoop cluster,the problem resolved。how to find the root casue for the problem? thks。 -- This message was sent by Atlassian JIRA (v6.2#6252)
[VOTE] Migration from subversion to git for version control
I have put together this proposal based on recent discussion on this topic. Please vote on the proposal. The vote runs for 7 days. 1. Migrate from subversion to git for version control. 2. Force-push to be disabled on trunk and branch-* branches. Applying changes from any of trunk/branch-* to any of branch-* should be through git cherry-pick -x. 3. Force-push on feature-branches is allowed. Before pulling in a feature, the feature-branch should be rebased on latest trunk and the changes applied to trunk through git rebase --onto or git cherry-pick commit-range. 4. Every time a feature branch is rebased on trunk, a tag that identifies the state before the rebase needs to be created (e.g. tag_feature_JIRA-2454_2014-08-07_rebase). These tags can be deleted once the feature is pulled into trunk and the tags are no longer useful. 5. The relevance/use of tags stay the same after the migration. Thanks Karthik PS: Per Andrew Wang, this should be a Adoption of New Codebase kind of vote and will be Lazy 2/3 majority of PMC members.
Re: [VOTE] Release Apache Hadoop 2.5.0 RC2
+1 non-binding + downloaded the source, built the tarball from it successfully + verified the dates of CHANGES.txt + ran a couple of MR example jobs successfully + ran DS jobs successfully + verified the applications' history was accessible from the timeline server + verified the DS jobs published the right entities and the events to the timeline server On Thu, Aug 7, 2014 at 6:28 PM, Andrew Wang andrew.w...@cloudera.com wrote: +1 binding * verified mds * built tarball from source * checked the CHANGES.txt files, they have dates * ran apache-rat:check * ran pseudo cluster from the resulting tarball, ran teragen, sort, validate on uncached and cached files On Thu, Aug 7, 2014 at 8:58 AM, Masatake Iwasaki iwasak...@oss.nttdata.co.jp wrote: +1 (non-binding) + verified MD5 for tarball and source tarball + built from source tarball + ran example jobs such as nutchindexing, wordcount, dfsioe, hivebench, kmeans, pagerank, bayes, sort, terasort with HiBench on the cluster with 3 slave nodes. (8/6/14, 13:59), Karthik Kambatla wrote: Hi folks, I have put together a release candidate (rc2) for Hadoop 2.5.0. The RC is available at: http://people.apache.org/~kasha/hadoop-2.5.0-RC2/ The RC tag in svn is here: https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.5.0-rc2/ The maven artifacts are staged at: https://repository.apache.org/content/repositories/orgapachehadoop-1009/ You can find my public key at: http://svn.apache.org/repos/asf/hadoop/common/dist/KEYS Please try the release and vote. The vote will run for the now usual 5 days. Thanks -- Zhijie Shen Hortonworks Inc. http://hortonworks.com/ -- 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.
