You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/02/23 03:49:19 UTC
[jira] [Updated] (BIGTOP-1195) Higher level interface to smokes.
[ https://issues.apache.org/jira/browse/BIGTOP-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jay vyas updated BIGTOP-1195:
-----------------------------
Attachment: BIGTOP-1195.patch
Okay, finally got some time to cleanup my test runners into a "pure" bigtop incantation.
This script will work to compile and run all the smoke tests on current bigtop , ive just tested it in VMs, and it should work right out of the box.
> 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, 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)