[
https://issues.apache.org/jira/browse/BIGTOP-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308636#comment-14308636
]
jay vyas commented on BIGTOP-1521:
----------------------------------
my original thought was :
- Test if a component is basically functioning before doing deeper tests (i.e.
confirm nodemanager is up before running a yarn job).
- then somehow my twisted brain turned that into a *DAG* which is a bit silly.
Now coming full circle, the purpose of this jira can be fixed, albeit
inelegantly, with a simple timeout :) that should solve the problem for us...
leave the fancy test dependency ideas/ pre-testing ideas for another day :)
> 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)
