Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 16 Nov 2012 08:54:12 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <1190178839.122993.1353056052673.JavaMail.jiratomcat@arcas>
In-Reply-To: <1220915979.122784.1353045731958.JavaMail.jiratomcat@arcas>
Subject: =?utf-8?Q?[jira]_[Commented]_(HADOOP?=
 =?utf-8?Q?-9051)_=E2=80=9Cant_test=E2=80=9D_will_bui?=
 =?utf-8?Q?ld_failed_for__trying_to_delete_an_non-existent_file?=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HADOOP-9051?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D134=
98679#comment-13498679 ]=20

Steve Loughran commented on HADOOP-9051:
----------------------------------------

Ant doesn't complain about deleting files/dirs that aren't there -otherwise=
 "ant clean" wouldn't be idempotent.

If it couldn't delete a file, then there's another cause -such as the file =
is in use.

Setting {{quiet=3Dtrue}} will keep the build going on after this -but the r=
oot cause is still lurking out there -maybe an MR process is still running.

Is this replicable on your system? if you insert an {{<exec command=3D"jps =
-v" />}} , what processes are seen to be running?
               =20
> =E2=80=9Cant test=E2=80=9D will build failed for  trying to delete an non=
-existent file
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-9051
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9051
>             Project: Hadoop Common
>          Issue Type: Test
>          Components: test
>    Affects Versions: 1.0.0
>         Environment: OS: Ubuntu 10.04; forrest version 0.8; findbugs vers=
ion 2.0.1; ant version 1.8.1
>            Reporter: meng gong
>            Priority: Minor
>              Labels: test
>             Fix For: 1.0.0
>
>         Attachments: fix-ant-test
>
>
> Run "ant test" on branch-1 of hadoop-common.
> When the test process reach "test-core-excluding-commit-and-smoke"
> It will invoke the "macro-test-runner" to clear and rebuild the test envi=
ronment.
> Then the ant task command  <delete dir=3D"@{test.dir}/logs" />
> failed for trying to delete an non-existent file.
> following is the test result logs:
> test-core-excluding-commit-and-smoke:
>    [delete] Deleting: /home/jdu/bdc/hadoop-topology-branch1-new/hadoop-co=
mmon/build/test/testsfailed
>    [delete] Deleting directory /home/jdu/bdc/hadoop-topology-branch1-new/=
hadoop-common/build/test/data
>     [mkdir] Created dir: /home/jdu/bdc/hadoop-topology-branch1-new/hadoop=
-common/build/test/data
>    [delete] Deleting directory /home/jdu/bdc/hadoop-topology-branch1-new/=
hadoop-common/build/test/logs
> BUILD FAILED
> /home/jdu/bdc/hadoop-topology-branch1-new/hadoop-common/build.xml:1212: T=
he following error occurred while executing this line:
> /home/jdu/bdc/hadoop-topology-branch1-new/hadoop-common/build.xml:1166: T=
he following error occurred while executing this line:
> /home/jdu/bdc/hadoop-topology-branch1-new/hadoop-common/build.xml:1057: U=
nable to delete file /home/jdu/bdc/hadoop-topology-branch1-new/hadoop-commo=
n/build/test/logs/userlogs/job_20121112223129603_0001/attempt_2012111222312=
9603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2012=
1112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/att=
empt_20121112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000=
000_0/attempt_20121112223129603_0001_r_000000_0/attempt_20121112223129603_0=
001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2012111222=
3129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2=
0121112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/=
attempt_20121112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_=
000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2012111222312960=
3_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2012111=
2223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attemp=
t_20121112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000=
_0/attempt_20121112223129603_0001_r_000000_0/attempt_20121112223129603_0001=
_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2012111222312=
9603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2012=
1112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/att=
empt_20121112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000=
000_0/attempt_20121112223129603_0001_r_000000_0/attempt_20121112223129603_0=
001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2012111222=
3129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/attempt_2=
0121112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_000000_0/=
attempt_20121112223129603_0001_r_000000_0/attempt_20121112223129603_0001_r_=
000000_0/stdout

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira