[
https://issues.apache.org/jira/browse/BIGTOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14180967#comment-14180967
]
jay vyas edited comment on BIGTOP-1493 at 10/23/14 3:39 AM:
------------------------------------------------------------
good point - the primary question is, i think, *is it valuable for us to
curate tests for components outside of Bigtop's packaging* ? ...
*The technical issues is easy to handle* : just configure it to only run tests
for stuff we package (as in BIGTOP-1449, which is the automated release
candidate tester ).
Are you (or anyone else) *theoretically against the idea of bigtop curating
tests for stuff that hasnt been packaged yet* ? Or is it just a technical
issue (i.e. that we dont want to add tests that will break things).
personally, I doubt that breaking the CI is going to be an issue : the
smoke-tests tests, and even the old test-artifacts tests, are both easy to
customize.
was (Author: jayunit100):
good point - the primary question is, i think, *is it valuable for us to
curate tests for components outside of Bigtop's packaging* ? ...
*The technical issues is easy to handle* : just configure it to only run tests
for stuff we package (as in BIGTOP-1449, which is the automated release
candidate tester ).
Are you (or anyone else) *theoretically against the idea of bigtop curating
tests for stuff that hasnt been packaged yet* ? Or is it just a technical
issue?
> Add smoke test for tachyon
> --------------------------
>
> Key: BIGTOP-1493
> URL: https://issues.apache.org/jira/browse/BIGTOP-1493
> Project: Bigtop
> Issue Type: Test
> Components: tests
> Reporter: jay vyas
>
> 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)
