[
https://issues.apache.org/jira/browse/BIGTOP-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307442#comment-14307442
]
jay vyas commented on BIGTOP-1521:
----------------------------------
[~dasha.boudnik] well, for example, i think {{hadoop fs -ls}} commands , if
failing, should trigger all tests to fail.
And, like if simple {{pi 2 2}} job fails, all other tests should fail.
No point in testing pig, hive if mapreduce is not working.
So we have a *DAG* of sorts. Should be quite possible to implement given the
fine grained and easily scripted controls that gradle allows us w/ task
dependencies.
> Bigtop smoke-tests hierarchy and fast failure
> ---------------------------------------------
>
> Key: BIGTOP-1521
> URL: https://issues.apache.org/jira/browse/BIGTOP-1521
> Project: Bigtop
> Issue Type: Bug
> Components: tests
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Assignee: Dasha Boudnik
>
> *Problem* Sometimes YARN jobs can hang indefinetly, and in the case of the
> {{smoke-tests}} , we also can get an infinite hang it appears.
> This can be reproduced by simply messing up/deleting the core hadoop
> components from {{bigtop-deploy/vm/vagrant-puppet}}'s provision script puppet
> conf file {{provision.sh}} and running {{vagrant up}}.
> *Solution* Let add some smarts to the smoke tester - such that the basic yarn
> services (i. think hadoop-smoke in test-artifcacts does this maybe ) are
> confirmed before any yarn based tests are ran.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
