[
https://issues.apache.org/jira/browse/BIGTOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211711#comment-14211711
]
Konstantin Boudnik commented on BIGTOP-1493:
--------------------------------------------
bq. I agree that its awkward. I need the examples jar and I need the hadoop
command
I think it is ok to require both env.vars to be set: HADOOP_HOME and
HADOOP_MARPEDUCE_HOME. We have some tests already that do exactly that.
bq. I rather that be a different JIRA, since its unknown what the effort to fix
it would be.
Ok, could you please open a ticket for that then?
bq. Currently the gradle tests do the same
True. Never mind - I thought that {{checkEnv}} is specific for the particular
test. Now I see that it is defined in the top level build file. Thanks
bq. {code}bigtop.default.logger=TRACE,A1
log4j.rootLogger=${bigtop.default.logger}{code}
I was rather hinting that we can be able to set logger level in the top-level
gradle file, instead of explicitly setting it in each test's build. That's why
I referred to the maven {{common}} module. Does it make more sense?
> Add smoke test for tachyon
> --------------------------
>
> Key: BIGTOP-1493
> URL: https://issues.apache.org/jira/browse/BIGTOP-1493
> Project: Bigtop
> Issue Type: Test
> Components: tests
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Assignee: David Capwell
> Attachments: BIGTOP-1493.1.patch
>
>
> Tachyon as an in memory cache will be emerging as a common feature in hadoop
> and spark based clusters.
> Lets create a smoke test under the {{smoke-tests}} which uses the
> {{tachyon:///}} url.
> To get started with the smoke tests, you can
> 1) Run the vagrant recipe under bigtop-deploy/vm/vagrant-puppet . This will
> demonstrate the way you spin up a bigtop based hadoop cluster.
> 2) Now, you can do {{vagrant ssh}} into your cluster, and simply edit the
> smoke tests or install stuff. Re running the smoke-tests.sh file should test
> that your new tests work . At that point, just exit your VM, and commit your
> changes and submit the new patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
