[
https://issues.apache.org/jira/browse/BIGTOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212655#comment-14212655
]
David Capwell commented on BIGTOP-1493:
---------------------------------------
bq. 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?
I agree that this is better. Might make even more sense to have each test use
the same log4j file as
{noformat}bigtop-tests/test-execution/common/pom.xml{noformat} does.
Because of the current way that things are setup, doing this would make sense
on its own JIRA. Ill file a jira for this
> 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)
