[
https://issues.apache.org/jira/browse/BIGTOP-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308516#comment-14308516
]
Konstantin Boudnik commented on BIGTOP-1521:
--------------------------------------------
Actually to build a *DAG* of a sort for tests you'd have to expose the
dependency knowledge about the tests all the way up to the build system; and
then you'll have to find a way to keep it in sync with the changing tests.
Also, arguably, a purpose of the integration tests is run them all and then see
what functionality (out of many) has failed. It's like configuring C-compiler
not to fail at the first error ;)
> 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)
