[
https://issues.apache.org/jira/browse/BIGTOP-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889739#comment-13889739
]
Konstantin Boudnik commented on BIGTOP-1195:
--------------------------------------------
I don't think we can do such separation. If you think about this - the only way
to test say Hbase binaries downloaded and built from apache.org is to setup
HDFS cluster, set up Hbase and ZK and the run some loads. Considering that we
do not deploy anything else but linux packages, the smoking of the binaries is
an integral part of smoking of the packages. I am not sure if it is feasible to
test binaries without deployment. Please provide me with more details if I am
missing something.
In the interest of full disclosure though, there's a way to test packages
functionality separately and that's what the package manager tests are for.
> Higher level interface to smokes.
> ---------------------------------
>
> Key: BIGTOP-1195
> URL: https://issues.apache.org/jira/browse/BIGTOP-1195
> Project: Bigtop
> Issue Type: Improvement
> Reporter: jay vyas
> Attachments: BIGTOP-1195.1.very-raw.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)
