I am also wondering whether current smoke test is too ambitious and we
probably should have just the minimal set of tests that can be run to test
the "basic" health of bigtop builds for each of its sub projects say
within 5 minutes with minimal dependencies.

Right now, only hadoop subproject can barely pass the smoke test after
applying several patches (including this ticket BIGTOP-483 and BIGTOP-488,
etc). See 
https://cwiki.apache.org/confluence/display/BIGTOP/Known+Working+Tests
which tracked some of the results. I am not sure others observed the same.

David

On 4/4/12 1:29 PM, "Konstantin Boudnik (Commented) (JIRA)"
<[email protected]> wrote:

>
>    [ 
>https://issues.apache.org/jira/browse/BIGTOP-483?page=com.atlassian.jira.p
>lugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246702#com
>ment-13246702 ] 
>
>Konstantin Boudnik commented on BIGTOP-483:
>-------------------------------------------
>
>Also, the question is: why all of a sudden that test doesn't pass
>anymore? It was there since the beginning and our development platform
>was Ubuntu. That makes one think...
>                
>> Smoke test of Hadoop fails with clitest missing testConf.xml file
>> -----------------------------------------------------------------
>>
>>                 Key: BIGTOP-483
>>                 URL: https://issues.apache.org/jira/browse/BIGTOP-483
>>             Project: Bigtop
>>          Issue Type: Bug
>>          Components: Tests
>>    Affects Versions: 0.3.0
>>         Environment: Found on ubuntu, but applies to all systems.
>>            Reporter: David Liu
>>            Assignee: Roman Shaposhnik
>>             Fix For: 0.4.0
>>
>>         Attachments: BIGTOP-483.patch.txt
>>
>>
>> 12/03/21 23:10:05 INFO cli.TestCLI: File:
>>/home/ubuntu/bigtop/bigtop-tests/test-execution/smokes/hadoop/target/clit
>>est_data/testConf.xml not found
>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.923
>>sec <<< FAILURE!
>> Results :
>> Failed tests: 
>>   testAll(org.apache.bigtop.itest.hadooptests.TestTestCLI)
>> Tests run: 10, Failures: 1, Errors: 0, Skipped: 0
>> More details:
>> 
>>-------------------------------------------------------------------------
>>------
>> Test set: org.apache.bigtop.itest.hadooptests.TestTestCLI
>> 
>>-------------------------------------------------------------------------
>>------
>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.923
>>sec <<< FAILURE!
>> testAll(org.apache.bigtop.itest.hadooptests.TestTestCLI)  Time elapsed:
>>0.096 sec  <<< FAILURE!
>> junit.framework.AssertionFailedError: Error reading test config file
>>         at junit.framework.Assert.fail(Assert.java:47)
>>         at junit.framework.Assert.assertTrue(Assert.java:20)
>>         at 
>>org.apache.hadoop.cli.TestCLI.readTestConfigFile(TestCLI.java:105)
>>         at org.apache.hadoop.cli.TestCLI.setUp(TestCLI.java:114)
>
>--
>This message is automatically generated by JIRA.
>If you think it was sent incorrectly, please contact your JIRA
>administrators: 
>https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>        


Reply via email to