You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Anatoli Fomenko (JIRA)" <ji...@apache.org> on 2013/04/10 03:45:14 UTC
[jira] [Comment Edited] (BIGTOP-895) A number of testcases in
TestCLI are failing with (at least) Hadoop 2.0.3 and later
[ https://issues.apache.org/jira/browse/BIGTOP-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626934#comment-13626934 ]
Anatoli Fomenko edited comment on BIGTOP-895 at 4/10/13 1:44 AM:
-----------------------------------------------------------------
In the course of investigation, updating current testConf.xml with ~140 tests to the new Hadoop smoke tests in testHDFSConf.xml with ~600 tests seemed to be proper.
It has been found that quite a few tests in testHDFSConf.xml, while passing on hadoop-common smoke infrastructure using a mini-cluster, fail on a default Bigtop cluster. There are a few unrelated reasons to that:
# The regexp for files in RegexpComparator in testHDFSConf.xml have a hard coded replication factor set to 1 that is fine for mini-cluster, but fails on a real cluster with a default replication factor set to 3. This issue should be resolved in HADOOP-9464.
# As opposed to Bigtop testConf.xml where default "root" working HDFS directory is set to /tmp/testcli, that is widely accessible, testHDFSConf.xml default HDFS directory is set to /. Since the "root" prefix needs to be prepended in each test case, a better solution would be to set HDFS / permission on a Bigtop cluster to 777.
# Output from test commands such as {code}-count -q /dir1{code} are entirely different on mini-cluster and Bigtop cluster.
# Some tests require superuser privileges that needs to be addressed per test case.
These issues are planned to be resolved. Also, a reuse of the Hadoop testHDFSConf.xml along with the majority of the test helping infrastructure will be achieved by making TestCLI class extending CLITestHelperDFS as opposed to current CLITestHelper.
was (Author: anatoli.fomenko):
In the course of investigation, updating current testConf.xml with ~140 tests to the new Hadoop smoke tests in testHDFSConf.xml with ~600 tests seemed to be proper.
It has been found that quite a few tests in testHDFSConf.xml, while passing on hadoop-common smoke infrastructure using a mini-cluster, fail on a default Bigtop cluster. There are a few unrelated reasons to that:
# The regexp for files in RexexpComparator in testHDFSConf.xml have a hard coded replication factor set to 1 that is fine for mini-cluster, but fails on a real cluster with a default replication factor set to 3. This issue should be resolved in HADOOP-9464.
# As opposed to Bigtop testConf.xml where default "root" working HDFS directory is set to /tmp/testcli, that is widely accessible, testHDFSConf.xml default HDFS directory is set to /. Since the "root" prefix needs to be prepended in each test case, a better solution would be to set HDFS / permission on a Bigtop cluster to 777.
# Output from test commands such as {code}-count -q /dir1{code} are entirely different on mini-cluster and Bigtop cluster.
# Some tests require superuser privileges that needs to be addressed per test case.
These issues are planned to be resolved. Also, a reuse of the Hadoop testHDFSConf.xml along with the majority of the test helping infrastructure will be achieved by making TestCLI class extending CLITestHelperDFS as opposed to current CLITestHelper.
> A number of testcases in TestCLI are failing with (at least) Hadoop 2.0.3 and later
> -----------------------------------------------------------------------------------
>
> Key: BIGTOP-895
> URL: https://issues.apache.org/jira/browse/BIGTOP-895
> Project: Bigtop
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.5.0
> Reporter: Konstantin Boudnik
> Assignee: Anatoli Fomenko
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: failing-testCLI.txt
>
>
> The list of failing tests is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira