[
https://issues.apache.org/jira/browse/BIGTOP-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916157#comment-13916157
]
Martin Bukatovic commented on BIGTOP-1195:
------------------------------------------
My feeling is that the most important thing here is to clearly document all the
assumptions (env variables, user, configuration) for running the bigtop smokes.
So far, we have this wikipage:
https://cwiki.apache.org/confluence/display/BIGTOP/Running+integration+and+system+tests
I for example miss here that you need to create new user account and setup
sudoers file for bigtop tests to work (as running under root is not a good idea
here).
That said, having an runner script would be great addition to that. I see the
reasons why it would be difficult to include it as a proper way to run tests,
but I would be ok with declaring the script as an example how one can run the
tests.
> Higher level interface to smokes.
> ---------------------------------
>
> Key: BIGTOP-1195
> URL: https://issues.apache.org/jira/browse/BIGTOP-1195
> Project: Bigtop
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 0.7.0
> Reporter: jay vyas
> Assignee: jay vyas
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1195.1.very-raw.patch, BIGTOP-1195.patch
>
>
> Running all the smokes with mvn verify is painful:
> 1) Diving into the XML files when stuff breaks
> 2) Remembering to use TRACE level logging
> 3) Leaving out export PIG_HOME , etc... leads to smokes failing late in the
> test run.
> 4) Hopefully we can specify more env variables to control size of smokes in
> the future. That will make a script for running the whole thing even more
> useful.
> 5) when hacking the groovy scripts:: To Compile or not to compile? Always
> forget to specify.
> A simple bash script could serve as a better tutorial/solution/template for
> users that want to run smokes. I'm attaching a very raw patch that we can
> rewrite in python and flesh out some more to do better error reporting, more
> verification, etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
