Bigtop
  1. Bigtop
  2. BIGTOP-1052

Increase environment configurability/debugging of Mahout Tests

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.6.0
    • Fix Version/s: 0.7.0
    • Component/s: tests
    • Labels:
      None

      Description

      The TestMahoutExamples.groovy file is very comprehensive but also very long and complex. There are other JIRA's that suggest that some of the tests in it fail. It is different from TestHadoopExamples in that it is not easy to comment out the subtests to only run a subset.

      I suggest

      1) [TO BE MOVED TO A SEPARATE JIRA] Refactoring tests into separate groovy scripts so that they can be filtered in the Pom, using the includes. i.e.

      <includes>
      <include>**/Test*MovieLens</include>
      </includes>

      And as another convenience for the purpose of easing the running of these tests, I suggest

      2) [THIS JIRA: 1052] Utilizing MAHOUT_HOME environmental variable in the tests if it is provided, so that the mahout package installation can be tested directly from tarballs.

        Activity

        jay vyas created issue -
        jay vyas made changes -
        Field Original Value New Value
        Description The TestMahoutExamples.groovy file is very comprehensive :) but also very long and complex. There are other JIRA's that suggest that some of the tests in it fail. It is different from TestHadoopExamples in that it is not easy to comment out the subtests to only run a subset.

        I suggest refactoring tests into separate groovy scripts so that they can be filtered in the Pom, using the includes. i.e.

        <includes>
           <include>**/*Test*MovieLens*</include>
        </includes>
        The TestMahoutExamples.groovy file is very comprehensive :) but also very long and complex. There are other JIRA's that suggest that some of the tests in it fail. It is different from TestHadoopExamples in that it is not easy to comment out the subtests to only run a subset.

        I suggest

        1) Refactoring tests into separate groovy scripts so that they can be filtered in the Pom, using the includes. i.e.

        <includes>
           <include>**/*Test*MovieLens*</include>
        </includes>

        And as another convenience for the purpose of easing the running of these tests, I suggest

        2) Utilizing MAHOUT_HOME environmental variable in the tests if it is provided, so that the mahout package installation can be tested directly from tarballs.
        jay vyas made changes -
        Description The TestMahoutExamples.groovy file is very comprehensive :) but also very long and complex. There are other JIRA's that suggest that some of the tests in it fail. It is different from TestHadoopExamples in that it is not easy to comment out the subtests to only run a subset.

        I suggest

        1) Refactoring tests into separate groovy scripts so that they can be filtered in the Pom, using the includes. i.e.

        <includes>
           <include>**/*Test*MovieLens*</include>
        </includes>

        And as another convenience for the purpose of easing the running of these tests, I suggest

        2) Utilizing MAHOUT_HOME environmental variable in the tests if it is provided, so that the mahout package installation can be tested directly from tarballs.
        The TestMahoutExamples.groovy file is very comprehensive :) but also very long and complex. There are other JIRA's that suggest that some of the tests in it fail. It is different from TestHadoopExamples in that it is not easy to comment out the subtests to only run a subset.

        I suggest

        1) [TO BE MOVED TO A SEPARATE JIRA] Refactoring tests into separate groovy scripts so that they can be filtered in the Pom, using the includes. i.e.

        <includes>
           <include>**/*Test*MovieLens*</include>
        </includes>

        And as another convenience for the purpose of easing the running of these tests, I suggest

        2) [THIS JIRA: 1052] Utilizing MAHOUT_HOME environmental variable in the tests if it is provided, so that the mahout package installation can be tested directly from tarballs.
        jay vyas made changes -
        Summary Increase pom.xml configurability of Mahout Tests Increase environment configurability/debugging of Mahout Tests
        jay vyas made changes -
        Attachment BIGTOP-1052.1.patch [ 12600190 ]
        Roman Shaposhnik made changes -
        Assignee jay vyas [ jayunit100 ]
        Roman Shaposhnik made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 0.7.0 [ 12324362 ]
        Resolution Fixed [ 1 ]
        Roman Shaposhnik made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Konstantin Boudnik made changes -
        Affects Version/s 0.6.0 [ 12323895 ]

          People

          • Assignee:
            jay vyas
            Reporter:
            jay vyas
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 24h
              24h
              Remaining:
              Remaining Estimate - 24h
              24h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development