Details

    • Type: Test Test
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.21.0, 0.22.0
    • Fix Version/s: 0.21.0
    • Component/s: build
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Most HDFS tests are functional tests that test a feature end to end by running a mini cluster. We should add more tests like TestReplication that attempt to stress individual classes in isolation, ie by stubbing out dependencies without running a mini cluster. This allows for more fine-grain testing and making tests run much more quickly because they avoid the cost of cluster setup and teardown. If it makes sense to use another framework besides junit we should standardize with MAPREDUCE-1050.

      1. HDFS-669.sh
        0.1 kB
        Konstantin Boudnik
      2. HDFS-669.patch
        4 kB
        Konstantin Boudnik
      3. HDFS-669.patch
        8 kB
        Konstantin Boudnik
      4. HDFS-669.patch
        9 kB
        Konstantin Boudnik
      5. HDFS-669.patch
        8 kB
        Konstantin Boudnik
      6. HDFS-669.patch
        8 kB
        Konstantin Boudnik
      7. HDFS-669.patch
        8 kB
        Konstantin Boudnik
      8. HDFS-669.patch
        8 kB
        Konstantin Boudnik
      9. HDFS669.patch
        5 kB
        Eli Collins

        Issue Links

          Activity

          Hide
          Eli Collins added a comment -

          Attached is a patch with a couple tests that exercise FSNamesystem directly. One tests rename in safe mode, the other the inode name quota (the latter is not a particularly great test since it can be easily verified at a higher-level but you get the idea). Each runs in less than a second on my laptop. NameNode's initMetrics method had to be made package rather than private. That could be avoided by using the reflection API (Field.setAccessible) when running the test.

          Show
          Eli Collins added a comment - Attached is a patch with a couple tests that exercise FSNamesystem directly. One tests rename in safe mode, the other the inode name quota (the latter is not a particularly great test since it can be easily verified at a higher-level but you get the idea). Each runs in less than a second on my laptop. NameNode's initMetrics method had to be made package rather than private. That could be avoided by using the reflection API (Field.setAccessible) when running the test.
          Hide
          Konstantin Boudnik added a comment -

          Seems interesting!

          While the following isn't related to the current patch, I'd like to make a clear point about adding new methods/APIs for pure testability purposes.

          If any new public methods are have to be introduce to facilitate the testing efforts then such methods ought to be add by the means of existing injection framework (see my comment on MAPREDUCE-1050) and not to be made a permanent addition to the production code.

          Show
          Konstantin Boudnik added a comment - Seems interesting! While the following isn't related to the current patch, I'd like to make a clear point about adding new methods/APIs for pure testability purposes. If any new public methods are have to be introduce to facilitate the testing efforts then such methods ought to be add by the means of existing injection framework (see my comment on MAPREDUCE-1050 ) and not to be made a permanent addition to the production code.
          Hide
          Konstantin Boudnik added a comment -

          I was trying to review it but patch doesn't apply anymore.

          Show
          Konstantin Boudnik added a comment - I was trying to review it but patch doesn't apply anymore.
          Hide
          Eli Collins added a comment -

          Hey Konstantin, I'll merge in the latest from trunk and update the patch. Also, per discussion with the other Konstantin I'll make the test cover NameNode instead of FSNamesystem.

          Show
          Eli Collins added a comment - Hey Konstantin, I'll merge in the latest from trunk and update the patch. Also, per discussion with the other Konstantin I'll make the test cover NameNode instead of FSNamesystem.
          Hide
          Konstantin Boudnik added a comment -

          Thanks Eli. Looking forward for the new version!

          Also, I've made some modifications of original MAPREDUCE-1050 which moved the true unit tests under src/test/unit. Also it adds a separate unit test target. I believe, it make sense to have a similar thing for HDFS.

          Show
          Konstantin Boudnik added a comment - Thanks Eli. Looking forward for the new version! Also, I've made some modifications of original MAPREDUCE-1050 which moved the true unit tests under src/test/unit . Also it adds a separate unit test target. I believe, it make sense to have a similar thing for HDFS.
          Hide
          Konstantin Boudnik added a comment -

          I'm sure you've noticed that already, but the test cases are failing with the following diagnostics:

          ...
          2009-11-09 12:33:37,906 INFO  metrics.FSNamesystemMetrics (FSNamesystemMetrics.java:<init>(78)) - Initializing FSNamesystemMetrics using context object:org.apache.hadoop.metrics.
          spi.NullContext
          2009-11-09 12:33:37,915 INFO  namenode.FSNamesystem (FSNamesystem.java:registerMBean(3991)) - Registered FSNamesystemStatusMBean
          2009-11-09 12:33:37,973 WARN  conf.Configuration (Configuration.java:handleDeprecation(326)) - fs.checkpoint.dir is deprecated. Instead, use dfs.namenode.checkpoint.dir
          2009-11-09 12:33:37,975 WARN  namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(350)) - Scheme is undefined for /tmp/hadoop-cos/dfs/name
          2009-11-09 12:33:37,975 WARN  namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(351)) - Please check your file system configuration in hdfs-site.xml
          2009-11-09 12:33:37,976 WARN  namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(350)) - Scheme is undefined for /tmp/hadoop-cos/dfs/name
          2009-11-09 12:33:37,976 WARN  namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(351)) - Please check your file system configuration in hdfs-site.xml
          2009-11-09 12:33:37,981 INFO  common.Storage (Storage.java:analyzeStorage(356)) - Storage directory /private/tmp/hadoop-cos/dfs/name does not exist.
          2009-11-09 12:33:37,985 ERROR namenode.FSNamesystem (FSNamesystem.java:<init>(244)) - FSNamesystem initialization failed.
          org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /private/tmp/hadoop-cos/dfs/name is in an inconsistent state: storage directory does not exist or is 
          not accessible.
                  at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:401)
                  at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:112)
                  at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:261)
                  at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:242)
                  at org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem.getNamesystem(TestFSNamesystem.java:49)
                  at org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem.testRenameInSafemode(TestFSNamesystem.java:54)
          ...
          
          Show
          Konstantin Boudnik added a comment - I'm sure you've noticed that already, but the test cases are failing with the following diagnostics: ... 2009-11-09 12:33:37,906 INFO metrics.FSNamesystemMetrics (FSNamesystemMetrics.java:<init>(78)) - Initializing FSNamesystemMetrics using context object:org.apache.hadoop.metrics. spi.NullContext 2009-11-09 12:33:37,915 INFO namenode.FSNamesystem (FSNamesystem.java:registerMBean(3991)) - Registered FSNamesystemStatusMBean 2009-11-09 12:33:37,973 WARN conf.Configuration (Configuration.java:handleDeprecation(326)) - fs.checkpoint.dir is deprecated. Instead, use dfs.namenode.checkpoint.dir 2009-11-09 12:33:37,975 WARN namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(350)) - Scheme is undefined for /tmp/hadoop-cos/dfs/name 2009-11-09 12:33:37,975 WARN namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(351)) - Please check your file system configuration in hdfs-site.xml 2009-11-09 12:33:37,976 WARN namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(350)) - Scheme is undefined for /tmp/hadoop-cos/dfs/name 2009-11-09 12:33:37,976 WARN namenode.FSNamesystem (FSNamesystem.java:getStorageDirs(351)) - Please check your file system configuration in hdfs-site.xml 2009-11-09 12:33:37,981 INFO common.Storage (Storage.java:analyzeStorage(356)) - Storage directory /private/tmp/hadoop-cos/dfs/name does not exist. 2009-11-09 12:33:37,985 ERROR namenode.FSNamesystem (FSNamesystem.java:<init>(244)) - FSNamesystem initialization failed. org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /private/tmp/hadoop-cos/dfs/name is in an inconsistent state: storage directory does not exist or is not accessible. at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:401) at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:112) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:261) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:242) at org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem.getNamesystem(TestFSNamesystem.java:49) at org.apache.hadoop.hdfs.server.namenode.TestFSNamesystem.testRenameInSafemode(TestFSNamesystem.java:54) ...
          Hide
          Konstantin Boudnik added a comment -

          Looks like at least these lines have to be present in getNamesystem call:

              FileSystem.setDefaultUri(conf, "hdfs://localhost:0");
              conf.set(DFSConfigKeys.DFS_NAMENODE_HTTP_ADDRESS_KEY, "0.0.0.0:0");
              NameNode.format(conf);
              return spy(new FSNamesystem(conf));
          

          then it works

          Show
          Konstantin Boudnik added a comment - Looks like at least these lines have to be present in getNamesystem call: FileSystem.setDefaultUri(conf, "hdfs://localhost:0"); conf.set(DFSConfigKeys.DFS_NAMENODE_HTTP_ADDRESS_KEY, "0.0.0.0:0"); NameNode.format(conf); return spy(new FSNamesystem(conf)); then it works
          Hide
          Eli Collins added a comment -

          Thanks Konstantin, I'll try to send out a new patch before the end of the week, if you've got cycles before then and want to respin the base patch feel free to do that and I can add Namenode tests later. Seems like we could do this with two checkins, one to setup the infrastructure and follow on ones that add unit tests themselves.

          Show
          Eli Collins added a comment - Thanks Konstantin, I'll try to send out a new patch before the end of the week, if you've got cycles before then and want to respin the base patch feel free to do that and I can add Namenode tests later. Seems like we could do this with two checkins, one to setup the infrastructure and follow on ones that add unit tests themselves.
          Hide
          Konstantin Boudnik added a comment -

          Sure Eli. I have something in the pipe which requires Mockito, so I'm gonna send new version of the patch by end of today and hopefully we'll have it committed tomorrow. I took the liberty to reassign the JIRA to me.

          Show
          Konstantin Boudnik added a comment - Sure Eli. I have something in the pipe which requires Mockito, so I'm gonna send new version of the patch by end of today and hopefully we'll have it committed tomorrow. I took the liberty to reassign the JIRA to me.
          Hide
          Konstantin Boudnik added a comment -

          This patch version is based on the original posted by Eli. The following modifications were made:

          • patch is merged with current trunk
          • true unit tests (as in FSNamesystem) are being placed under src/test/unit
          • new build target 'run-test-unit' has been added to run unit tests only. This target is also included into test-core
          • original test is fixed and moved under src/test/unit from its original location
          Show
          Konstantin Boudnik added a comment - This patch version is based on the original posted by Eli. The following modifications were made: patch is merged with current trunk true unit tests (as in FSNamesystem) are being placed under src/test/unit new build target 'run-test-unit' has been added to run unit tests only. This target is also included into test-core original test is fixed and moved under src/test/unit from its original location
          Hide
          Konstantin Boudnik added a comment -

          Jakob has suggested to use JUnit's expected notation instead of the trick with assertion. Implemented.

          Show
          Konstantin Boudnik added a comment - Jakob has suggested to use JUnit's expected notation instead of the trick with assertion. Implemented.
          Hide
          Konstantin Boudnik added a comment -

          Slight modification to use JUnit provided setup and teardown facilities instead of manual setting and cleaning the resources before and after each test case.

          Show
          Konstantin Boudnik added a comment - Slight modification to use JUnit provided setup and teardown facilities instead of manual setting and cleaning the resources before and after each test case.
          Hide
          Konstantin Boudnik added a comment -

          Missing JavaDocs are also added

          Show
          Konstantin Boudnik added a comment - Missing JavaDocs are also added
          Hide
          Jakob Homan added a comment -
          • I ran with the patch and using -Dtestcase=TestFSNamesystem and the test was executed twice.
          • The testDirNQuota() test concerns me as it is not readily apparent what role the spied-on instance is playing and thus may not be a good example of how to use Mockito. At the very least, an explanation of how the spy is playing a role would be good. This is comparison to the other test, where it is clear that the isInSameMode() call is intercepted and re-defined.
          Show
          Jakob Homan added a comment - I ran with the patch and using -Dtestcase=TestFSNamesystem and the test was executed twice. The testDirNQuota() test concerns me as it is not readily apparent what role the spied-on instance is playing and thus may not be a good example of how to use Mockito. At the very least, an explanation of how the spy is playing a role would be good. This is comparison to the other test, where it is clear that the isInSameMode() call is intercepted and re-defined.
          Hide
          Konstantin Boudnik added a comment -

          Duplication of testcase execution is fixed. Now junit will be looking for the specified testcase under an appropriate suite.type directory. E.g. if 'run-test-unit' is executed then only src/test/unit will be explored, etc.

          A comment is added for the questionable testcase explaining why it worth including.

          Show
          Konstantin Boudnik added a comment - Duplication of testcase execution is fixed. Now junit will be looking for the specified testcase under an appropriate suite.type directory. E.g. if 'run-test-unit' is executed then only src/test/unit will be explored, etc. A comment is added for the questionable testcase explaining why it worth including.
          Hide
          Konstantin Boudnik added a comment -

          After another conversation with Jakob I've bought his point that while the second test case is Ok example of a true unit test, it isn't a good example of how to use Mockito framework.

          I've removed it completely.

          Show
          Konstantin Boudnik added a comment - After another conversation with Jakob I've bought his point that while the second test case is Ok example of a true unit test, it isn't a good example of how to use Mockito framework. I've removed it completely.
          Hide
          Konstantin Boudnik added a comment -

          Ready for the verification

          Show
          Konstantin Boudnik added a comment - Ready for the verification
          Hide
          Jakob Homan added a comment -

          Cool, Cos. I'll look at it first thing in the morning.

          Show
          Jakob Homan added a comment - Cool, Cos. I'll look at it first thing in the morning.
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12424661/HDFS-669.patch
          against trunk revision 835179.

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 6 new or modified tests.

          +1 javadoc. The javadoc tool did not generate any warning messages.

          -1 javac. The applied patch generated 22 javac compiler warnings (more than the trunk's current 20 warnings).

          +1 findbugs. The patch does not introduce any new Findbugs warnings.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          -1 core tests. The patch failed core unit tests.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/71/testReport/
          Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/71/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
          Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/71/artifact/trunk/build/test/checkstyle-errors.html
          Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/71/console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12424661/HDFS-669.patch against trunk revision 835179. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The applied patch generated 22 javac compiler warnings (more than the trunk's current 20 warnings). +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/71/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/71/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/71/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/71/console This message is automatically generated.
          Hide
          Konstantin Boudnik added a comment -

          I'd suggest to move any tests out of the scope of this patch. The test in question is testing a deprecated method (thus two extra warnings).

          Current patch represents all needed modifications to add just Mockito framework.

          Show
          Konstantin Boudnik added a comment - I'd suggest to move any tests out of the scope of this patch. The test in question is testing a deprecated method (thus two extra warnings). Current patch represents all needed modifications to add just Mockito framework.
          Hide
          Konstantin Boudnik added a comment -

          Also, it seems that ivy hasn't downloaded mockito jar after the patch has been applied. Weird...

          Show
          Konstantin Boudnik added a comment - Also, it seems that ivy hasn't downloaded mockito jar after the patch has been applied. Weird...
          Hide
          Konstantin Boudnik added a comment -

          Script to create and add unit tests folder to the SVN

          Show
          Konstantin Boudnik added a comment - Script to create and add unit tests folder to the SVN
          Hide
          Jakob Homan added a comment -

          OK, latest patch looks fine once the script has been run (or the unit directory manually created). +1

          Of note, I tried adding a unit test into the commit-test.txt and running ant run-commit-test, but the unit test was not executed. This should be fixed so that unit tests included in the file are run, since hopefully that will be the source of most of them.

          Also, another JIRA should be opened to change the directory from hdfs to functional, so that we can start separating out the tests and not have a confusing directory name.

          As part of test-patch it may be worth enforcing that all tests included in /unit don't run more than a few seconds. This will provide a bit of a stick for enforcing that we end up with only real unit tests.

          Show
          Jakob Homan added a comment - OK, latest patch looks fine once the script has been run (or the unit directory manually created). +1 Of note, I tried adding a unit test into the commit-test.txt and running ant run-commit-test, but the unit test was not executed. This should be fixed so that unit tests included in the file are run, since hopefully that will be the source of most of them. Also, another JIRA should be opened to change the directory from hdfs to functional, so that we can start separating out the tests and not have a confusing directory name. As part of test-patch it may be worth enforcing that all tests included in /unit don't run more than a few seconds. This will provide a bit of a stick for enforcing that we end up with only real unit tests.
          Hide
          Jakob Homan added a comment -

          Latest version still needs hudson, right?

          Show
          Jakob Homan added a comment - Latest version still needs hudson, right?
          Hide
          Konstantin Boudnik added a comment -

          Let's roll

          Show
          Konstantin Boudnik added a comment - Let's roll
          Hide
          Konstantin Boudnik added a comment -

          Of note, I tried adding a unit test into the commit-test.txt and running ant run-commit-test, but the unit test was not executed. This should be fixed so that unit tests included in the file are run, since hopefully that will be the source of most of them.

          That's because current commit target isn't aware about unit tests. I believe, adding this has to be done separately when we'll start getting a significant amount of unit tests in place.

          Also, another JIRA should be opened to change the directory from hdfs to functional, so that we can start separating out the tests and not have a confusing directory name.

          Agree also, but perhaps as another JIRA?

          As part of test-patch it may be worth enforcing that all tests included in /unit don't run more than a few seconds. This will provide a bit of a stick for enforcing that we end up with only real unit tests.

          This is surely has to addressed separately.

          Show
          Konstantin Boudnik added a comment - Of note, I tried adding a unit test into the commit-test.txt and running ant run-commit-test, but the unit test was not executed. This should be fixed so that unit tests included in the file are run, since hopefully that will be the source of most of them. That's because current commit target isn't aware about unit tests. I believe, adding this has to be done separately when we'll start getting a significant amount of unit tests in place. Also, another JIRA should be opened to change the directory from hdfs to functional, so that we can start separating out the tests and not have a confusing directory name. Agree also, but perhaps as another JIRA? As part of test-patch it may be worth enforcing that all tests included in /unit don't run more than a few seconds. This will provide a bit of a stick for enforcing that we end up with only real unit tests. This is surely has to addressed separately.
          Hide
          Jakob Homan added a comment -

          I take back the Hudson comment. Hudson will bomb without the new unit directory. the current, stripped-down version of the patch doesn't include any Java, so Hudson won't be helpful. +1 on going without it.

          Show
          Jakob Homan added a comment - I take back the Hudson comment. Hudson will bomb without the new unit directory. the current, stripped-down version of the patch doesn't include any Java, so Hudson won't be helpful. +1 on going without it.
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12424759/HDFS-669.sh
          against trunk revision 835534.

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 2 new or modified tests.

          -1 patch. The patch command could not apply the patch.

          Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/74/console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12424759/HDFS-669.sh against trunk revision 835534. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 2 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/74/console This message is automatically generated.
          Hide
          Konstantin Boudnik added a comment -

          As expected, Hudson had choked on this. Considering that the patch is modifying build only and it has been tested manually a number of times, I'm going to commit it.

          Show
          Konstantin Boudnik added a comment - As expected, Hudson had choked on this. Considering that the patch is modifying build only and it has been tested manually a number of times, I'm going to commit it.
          Hide
          Eli Collins added a comment -

          The patch looks good to me. Thanks Konstantin.

          Show
          Eli Collins added a comment - The patch looks good to me. Thanks Konstantin.
          Hide
          Konstantin Boudnik added a comment -

          I've just committed this.

          It's also going to be backported to 0.21 to allow new Mockito based tests for append to be executed.

          Show
          Konstantin Boudnik added a comment - I've just committed this. It's also going to be backported to 0.21 to allow new Mockito based tests for append to be executed.
          Hide
          Konstantin Boudnik added a comment -

          Merged into branch 0.21 as well.

          Show
          Konstantin Boudnik added a comment - Merged into branch 0.21 as well.
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Hdfs-trunk-Commit #108 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/108/)
          . Add unit tests framework (Mockito). Contributed by Konstantin Boudnik, Eli Collins.

          Show
          Hudson added a comment - Integrated in Hadoop-Hdfs-trunk-Commit #108 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/108/ ) . Add unit tests framework (Mockito). Contributed by Konstantin Boudnik, Eli Collins.
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Hdfs-trunk-Commit #110 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/110/)

          Show
          Hudson added a comment - Integrated in Hadoop-Hdfs-trunk-Commit #110 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/110/ )
          Hide
          Hudson added a comment -

          Integrated in Hadoop-Hdfs-trunk #141 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk/141/)

          Show
          Hudson added a comment - Integrated in Hadoop-Hdfs-trunk #141 (See http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk/141/ )
          Hide
          Hudson added a comment -

          Integrated in Hdfs-Patch-h2.grid.sp2.yahoo.net #76 (See http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/76/)
          . Adding an 0-lenght .gitignore file to workaround git-svn issue with not synching empty folders. (cos)
          . Add unit tests framework (Mockito). Contributed by Konstantin Boudnik, Eli Collins.

          Show
          Hudson added a comment - Integrated in Hdfs-Patch-h2.grid.sp2.yahoo.net #76 (See http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h2.grid.sp2.yahoo.net/76/ ) . Adding an 0-lenght .gitignore file to workaround git-svn issue with not synching empty folders. (cos) . Add unit tests framework (Mockito). Contributed by Konstantin Boudnik, Eli Collins.
          Hide
          Hudson added a comment -

          Integrated in Hdfs-Patch-h5.grid.sp2.yahoo.net #115 (See http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/115/)

          Show
          Hudson added a comment - Integrated in Hdfs-Patch-h5.grid.sp2.yahoo.net #115 (See http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/115/ )

            People

            • Assignee:
              Konstantin Boudnik
              Reporter:
              Eli Collins
            • Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development