[jira] Created: (HDFS-901) Fedora jdk install creates circular symlinks, causes test-c++-libhdfs not to build

2010-01-14 Thread robert Cook (JIRA)
Fedora jdk install creates circular symlinks, causes test-c++-libhdfs not to 
build
--

 Key: HDFS-901
 URL: https://issues.apache.org/jira/browse/HDFS-901
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: build
Affects Versions: 0.20.1
 Environment: Fedora 2.6.26.8.fc8; hadoop 0.20.1; java 1.6.0_17
Reporter: robert Cook
Priority: Minor


installed hadoop; needed javac; installed jdk
export JAVA_HOME=/usr/java/jdk1.6.0_17
ant clean
ant
ant -Dcompile.c++=true -Dlibhdfs=true test-c++-libhdfs
---
[exec] libtool: link: gcc -g -O2 -DOS_LINUX -DDSO_DLFCN -DCPU=\"i386\" -m32 
-I/usr/java/jdk1.6.0_17/include -I/usr/java/jdk1.6.0_17/include/linux -Wall 
-Wstrict-prototypes -m32 /usr/java/jdk1.6.0_17/jre1.6.0_17/lib/i386/server 
-Wl,-x -o hdfs_test hdfs_test.o  -L/usr/java/jdk1.6.0_17/jre/lib/i386/server 
/home/cook/Desktop/hadoop-0.20.1/build/c++/Linux-i386-32/lib/libhdfs.so -ljvm 
-ldl -lpthread -Wl,-rpath 
-Wl,/home/cook/Desktop/hadoop-0.20.1/build/c++/Linux-i386-32/lib -Wl,-rpath 
-Wl,/home/cook/Desktop/hadoop-0.20.1/build/c++/Linux-i386-32/lib
 [exec] /usr/java/jdk1.6.0_17/jre1.6.0_17/lib/i386/server: file not 
recognized: Is a directory
 [exec] collect2: ld returned 1 exit status
 [exec] make: *** [hdfs_test] Error 1

BUILD FAILED
note: insertion of /usr/java/jdk1.6.0_17/jre1.6.0_17/lib/i386/server is spurious
---
tracked bug down as follows:
for some reason, install of jdk creates a symlink from within jdk directory to 
existing jre impl jre1.6.0_17 and a symlink from within jre directory to jdk.
I suspected the recursion likely messed up a "find" somewhere; deleted symlink 
in jdk then
ant clean
ant
ant -Dcompile.c++=true -Dlibhdfs=true test-c++-libhdfs
BUILD and TEST ran successfully then
just to be sure I put the symlink back; reran above; same failure

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Reopened: (HDFS-187) TestStartup fails if hdfs is running in the same machine

2010-01-14 Thread Tsz Wo (Nicholas), SZE (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo (Nicholas), SZE reopened HDFS-187:
-


> Hi Nicholas. I think this should be committed to branch-0.21 and branch-0.20 
> as well. ...
Sure.

Reopen for committing it to 0.20 and 0.21.

> TestStartup fails if hdfs is running in the same machine
> 
>
> Key: HDFS-187
> URL: https://issues.apache.org/jira/browse/HDFS-187
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: test
>Affects Versions: 0.21.0, 0.22.0
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Todd Lipcon
> Fix For: 0.22.0
>
> Attachments: hdfs-187-0.20.txt, hdfs-187.txt
>
>
> Reproduce this:
> - ./bin/start-dfs
> - ant test-core -Dtestcase=TestStartup
> The test may fail.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Resolved: (HDFS-187) TestStartup fails if hdfs is running in the same machine

2010-01-14 Thread Tsz Wo (Nicholas), SZE (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tsz Wo (Nicholas), SZE resolved HDFS-187.
-

   Resolution: Fixed
Fix Version/s: 0.21.0
   0.20.2

I have committed this also to 0.20 and 0.21.

> TestStartup fails if hdfs is running in the same machine
> 
>
> Key: HDFS-187
> URL: https://issues.apache.org/jira/browse/HDFS-187
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: test
>Affects Versions: 0.21.0, 0.22.0
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Todd Lipcon
> Fix For: 0.20.2, 0.21.0, 0.22.0
>
> Attachments: hdfs-187-0.20.txt, hdfs-187.txt
>
>
> Reproduce this:
> - ./bin/start-dfs
> - ant test-core -Dtestcase=TestStartup
> The test may fail.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Resolved: (HDFS-745) TestFsck timeout on 0.20.

2010-01-14 Thread Todd Lipcon (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HDFS-745.
--

   Resolution: Fixed
Fix Version/s: 0.20.2
 Assignee: Tsz Wo (Nicholas), SZE

This was fixed by reverting HDFS-127 from branch-0.20

> TestFsck timeout on 0.20.
> -
>
> Key: HDFS-745
> URL: https://issues.apache.org/jira/browse/HDFS-745
> Project: Hadoop HDFS
>  Issue Type: Bug
>Reporter: Tsz Wo (Nicholas), SZE
>Assignee: Tsz Wo (Nicholas), SZE
> Fix For: 0.20.2
>
>
> When I was testing HDFS-732 on 0.20, TestFsck kept timeout.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Resolved: (HDFS-734) TestDatanodeBlockScanner times out in branch 0.20

2010-01-14 Thread Todd Lipcon (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Todd Lipcon resolved HDFS-734.
--

Resolution: Duplicate
  Assignee: Tsz Wo (Nicholas), SZE  (was: Todd Lipcon)

This is fixed by Nicholas's revert of HDFS-127 on branch-0.20 (confirmed with a 
fresh checkout)

> TestDatanodeBlockScanner times out in branch 0.20
> -
>
> Key: HDFS-734
> URL: https://issues.apache.org/jira/browse/HDFS-734
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: test
>Reporter: Hairong Kuang
>Assignee: Tsz Wo (Nicholas), SZE
>Priority: Blocker
> Fix For: 0.20.2
>
>
> When I test HDFS-723 on branch 0.20, TestDatanodeBlockScanner always times 
> out with or without my patch to HDFS-723.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (HDFS-902) TestRaidNode fails

2010-01-14 Thread Eli Collins (JIRA)
TestRaidNode fails
--

 Key: HDFS-902
 URL: https://issues.apache.org/jira/browse/HDFS-902
 Project: Hadoop HDFS
  Issue Type: Test
Reporter: Eli Collins


The test-contrib test TestRaidNode fails because of a protocol version mismatch 
due to mapred jars checked into src/contrib/raid/lib. Updating them with jars 
from a fresh makes the test pass. Seems like we should nuke that directory, and 
either use mvn to fetch the appropriate jars or move this particular test over 
to the mapred respository.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.