Return-Path: Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: (qmail 90992 invoked from network); 6 Jan 2011 23:09:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Jan 2011 23:09:06 -0000 Received: (qmail 34524 invoked by uid 500); 6 Jan 2011 23:09:06 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 34462 invoked by uid 500); 6 Jan 2011 23:09:06 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 34449 invoked by uid 99); 6 Jan 2011 23:09:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jan 2011 23:09:06 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Jan 2011 23:09:06 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p06N8jkV001024 for ; Thu, 6 Jan 2011 23:08:45 GMT Message-ID: <8945342.200931294355325867.JavaMail.jira@thor> Date: Thu, 6 Jan 2011 18:08:45 -0500 (EST) From: "Todd Lipcon (JIRA)" To: mapreduce-issues@hadoop.apache.org Subject: [jira] Commented: (MAPREDUCE-2238) Undeletable build directories In-Reply-To: <20717354.120061294095526523.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978561#action_12978561 ] Todd Lipcon commented on MAPREDUCE-2238: ---------------------------------------- I think we should do the following: - change out the implementation of setPermissions to not use the Java APIs, but rather the old style system("chmod") approach - implement a proper chmod call in libhadoop (JNI) to avoid the fork for production systems where the fork is too expensive bq. Sorry...there are lots of interesting failure modes in Hadoop, and my memory is finite :) But that's why Hadoop's so much fun to work on! If it just worked all the time we'd be bored. > Undeletable build directories > ------------------------------ > > Key: MAPREDUCE-2238 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-2238 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: build, test > Affects Versions: 0.23.0 > Reporter: Eli Collins > > The MR hudson job is failing, looks like it's due to a test chmod'ing a build directory so the checkout can't clean the build dir. > https://hudson.apache.org/hudson/job/Hadoop-Mapreduce-trunk/549/console > Building remotely on hadoop7 > hudson.util.IOException2: remote file operation failed: /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk at hudson.remoting.Channel@2545938c:hadoop7 > at hudson.FilePath.act(FilePath.java:749) > at hudson.FilePath.act(FilePath.java:735) > at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:589) > at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:537) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1116) > at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411) > at hudson.model.Run.run(Run.java:1324) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:139) > Caused by: java.io.IOException: Unable to delete /grid/0/hudson/hudson-slave/workspace/Hadoop-Mapreduce-trunk/trunk/build/test/logs/userlogs/job_20101230131139886_0001/attempt_20101230131139886_0001_m_000000_0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.