Build failed in Jenkins: Hadoop-Common-0.23-Build #276

2012-06-06 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Common-0.23-Build/276/ -- [...truncated 13274 lines...] Running org.apache.hadoop.fs.viewfs.TestViewFsWithAuthorityLocalFs Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.125 sec Running

[jira] [Resolved] (HADOOP-8368) Use CMake rather than autotools to build native code

2012-06-06 Thread Alejandro Abdelnur (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur resolved HADOOP-8368. Resolution: Fixed I've reverted Nicholas revert from trunk branch-2, cleanly in

Re: Clarification about 2.* branches

2012-06-06 Thread Vinod Kumar Vavilapalli
I checked with Nicholas also who did the only merge into branch-2.0.0-alpha after the release and got a confirmation that I can delete the branch. Removing the branch now. Thanks, +Vinod On Jun 5, 2012, at 5:45 PM, Arun C Murthy wrote: +1 for blowing away branch-2.0.0-alpha now, we have

Re: Clarification about 2.* branches

2012-06-06 Thread Eli Collins
On Wed, Jun 6, 2012 at 2:10 PM, Eli Collins e...@cloudera.com wrote: Hey Vinod, Out of curiosity, why delete the branch?  Might make spelunking for svn revs that correspond to a release hard.  If we're deleting old release branches might as well delete the others (branch-0.23.0,

Re: Clarification about 2.* branches

2012-06-06 Thread Vinod Kumar Vavilapalli
Not sure when it stopped being so, but we always created release tags for the releases and do away with the staging branches. I find it confusing as to which branches to commit to when we have dead branches lying around. Regarding 0.23.*, you are right, I was about to send a separate email

Re: Clarification about 2.* branches

2012-06-06 Thread Vinod Kumar Vavilapalli
Done with deletion of the staging branch. Also updated all CHANGES.txt to point to a running branch-2 instead of a release. When we decide to make a release branch, we can separate sections then. Thanks, +vinod On Jun 5, 2012, at 4:40 PM, Vinod Kumar Vavilapalli wrote: Hi, I see two

[jira] [Created] (HADOOP-8487) Address test failures related to Windows paths not being valid DFS paths

2012-06-06 Thread Ivan Mitic (JIRA)
Ivan Mitic created HADOOP-8487: -- Summary: Address test failures related to Windows paths not being valid DFS paths Key: HADOOP-8487 URL: https://issues.apache.org/jira/browse/HADOOP-8487 Project: Hadoop

[jira] [Resolved] (HADOOP-8483) test-patch +1 even there are build failures

2012-06-06 Thread Colin Patrick McCabe (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-8483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe resolved HADOOP-8483. -- Resolution: Duplicate See INFRA-4886 test-patch +1 even

[jira] [Created] (HADOOP-8488) when Jenkins tests a patch, it should compile with -Pnative

2012-06-06 Thread Colin Patrick McCabe (JIRA)
Colin Patrick McCabe created HADOOP-8488: Summary: when Jenkins tests a patch, it should compile with -Pnative Key: HADOOP-8488 URL: https://issues.apache.org/jira/browse/HADOOP-8488

[jira] [Created] (HADOOP-8489) fix 32-bit native build on 64-bit x86

2012-06-06 Thread Colin Patrick McCabe (JIRA)
Colin Patrick McCabe created HADOOP-8489: Summary: fix 32-bit native build on 64-bit x86 Key: HADOOP-8489 URL: https://issues.apache.org/jira/browse/HADOOP-8489 Project: Hadoop Common