incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roman Shaposhnik (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BIGTOP-545) package testing manifest in trunk needs to be updated
Date Thu, 19 Apr 2012 01:26:40 GMT

    [ https://issues.apache.org/jira/browse/BIGTOP-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257137#comment-13257137
] 

Roman Shaposhnik commented on BIGTOP-545:
-----------------------------------------

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:
{noformat}
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*'
{noformat}

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.
                
> package testing manifest in trunk needs to be updated
> -----------------------------------------------------
>
>                 Key: BIGTOP-545
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-545
>             Project: Bigtop
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 0.4.0
>            Reporter: Roman Shaposhnik
>            Assignee: Roman Shaposhnik
>             Fix For: 0.4.0
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message