Bigtop
  1. Bigtop
  2. BIGTOP-545

package testing manifest in trunk needs to be updated

    Details

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

      Description

      We have quite a bit of issues in the manifest. Good news is that since I've resurrected nightly package test runs:
      http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-packagetest/
      we have to start (slowly) updating the manifest to match the reality.

      This will be a JIRA that doesn't get closed for a quite a bit, since I intend to do small commits on it.

        Activity

        Hide
        bikramjit ganguly added a comment -

        Roman, is this something on which i can work a little bit, or would it be too technical for me
        can you point a specific sub-issue, that i could potentially take a shot at?
        If emails are too time-consuming, maybe i could drop by your office sometime afterhours, and you could quickly show me what the issue is? or, if you live somewhere near the biocurious offices, we could meetup there, briefly? without some basic direction, i am not finding myself making much progress. thanks.

        Show
        bikramjit ganguly added a comment - Roman, is this something on which i can work a little bit, or would it be too technical for me can you point a specific sub-issue, that i could potentially take a shot at? If emails are too time-consuming, maybe i could drop by your office sometime afterhours, and you could quickly show me what the issue is? or, if you live somewhere near the biocurious offices, we could meetup there, briefly? without some basic direction, i am not finding myself making much progress. thanks.
        Hide
        Roman Shaposhnik added a comment -

        bikramjit, if you can help us clean it up I will personally buy you a beer. Seriously

        Here's the deal: the way to run package tests is pretty simple right now, just take a look at how we do it on jenkins. Essentially all you have to do is checkout the workspace in a VM (DO NOT RUN IT ON YOUR BOX) and then:

        export HADOOP_HOME=/usr/lib/hadoop
        export HADOOP_CONF=/etc/hadoop/conf
        mvn -f bigtop-tests/test-execution/package/pom.xml clean verify 
        -Dcdh.repo.file.url="${REPO_FILE_URL}" 
        -Dorg.apache.bigtop.itest.log4j.level=TRACE 
        -Dlog4j.debug=true 
        -Dorg.apache.maven-failsafe-plugin.testInclude='**/TestPackagesBasics*'
        

        You have to make sure that REPO_FILE_URL points to one of the same repo files you'd wget/curl in order to install Bigtop's trunk from here: http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Repository/

        Once the package tests are done running you'll see the results of the testing in bigtop-tests/test-execution/package/target/failsafe-reports/*.xml

        You can go line by line trying to see what's wrong or you can use one of the visualization tools.

        The basic idea is to update the .xml manifest files that we have under bigtop-tests/test-artifacts/package/src/main/resources to match what's currently inside of the packages. For not its mostly little stuff like metadata not matching, etc. But every bit helps.

        Finally, I would really appreciate if you could start up a wiki summarizing your experience doing package manifest cleanup. Future Bigtop contributors will buy you beer

        And of course it is totally ok to drop by. Reach out to me via email to set date/time.

        Show
        Roman Shaposhnik added a comment - bikramjit, if you can help us clean it up I will personally buy you a beer. Seriously Here's the deal: the way to run package tests is pretty simple right now, just take a look at how we do it on jenkins. Essentially all you have to do is checkout the workspace in a VM (DO NOT RUN IT ON YOUR BOX) and then: export HADOOP_HOME=/usr/lib/hadoop export HADOOP_CONF=/etc/hadoop/conf mvn -f bigtop-tests/test-execution/package/pom.xml clean verify -Dcdh.repo.file.url="${REPO_FILE_URL}" -Dorg.apache.bigtop.itest.log4j.level=TRACE -Dlog4j.debug=true -Dorg.apache.maven-failsafe-plugin.testInclude='**/TestPackagesBasics*' You have to make sure that REPO_FILE_URL points to one of the same repo files you'd wget/curl in order to install Bigtop's trunk from here: http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-Repository/ Once the package tests are done running you'll see the results of the testing in bigtop-tests/test-execution/package/target/failsafe-reports/*.xml You can go line by line trying to see what's wrong or you can use one of the visualization tools. The basic idea is to update the .xml manifest files that we have under bigtop-tests/test-artifacts/package/src/main/resources to match what's currently inside of the packages. For not its mostly little stuff like metadata not matching, etc. But every bit helps. Finally, I would really appreciate if you could start up a wiki summarizing your experience doing package manifest cleanup. Future Bigtop contributors will buy you beer And of course it is totally ok to drop by. Reach out to me via email to set date/time.

          People

          • Assignee:
            Roman Shaposhnik
            Reporter:
            Roman Shaposhnik
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development