You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2014/11/13 05:32:34 UTC
[jira] [Commented] (BIGTOP-1521) Bigtop smoke-tests hierarchy and
fast failure
[ https://issues.apache.org/jira/browse/BIGTOP-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209250#comment-14209250 ]
Konstantin Boudnik commented on BIGTOP-1521:
--------------------------------------------
[~jayunit100], I think the easier way to deal with this sort of problem is by introducing timeout to our tests. Thoughts?
> 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
>
> *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 replacing the 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)