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

See -- [...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 org.apach

[jira] [Created] (HADOOP-8486) Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor

Kanna Karanam created HADOOP-8486: - Summary: Resource leak - Close the open resource handles (File handles) before throwing the exception from the SequenceFile constructor Key: HADOOP-8486 URL: https://issues.apac

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

[ 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

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 t

Re: Clarification about 2.* branches

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, branch-0.23.0-rc0, branch-0.23.1, branch-0.23.2, etc) as well? Thanks, Eli On Wed, Ju

Re: Clarification about 2.* branches

On Wed, Jun 6, 2012 at 2:10 PM, Eli Collins 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, > branch-0.23.0-rc0, branc

Re: Clarification about 2.* branches

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 rega

Re: Clarification about 2.* branches

Makes sense. Thanks Vinod. On Wed, Jun 6, 2012 at 2:16 PM, Vinod Kumar Vavilapalli wrote: > > 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

Re: Clarification about 2.* branches

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 b

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

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

[ 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 the

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

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 Project:

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

[ https://issues.apache.org/jira/browse/HADOOP-8483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE reopened HADOOP-8483: Hi Colin, I think this is different from INFRA-4886. No matter what options

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

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