[jira] [Comment Edited] (BIGTOP-2100) Build from source errors out at test stage

["Evans Ye (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979974#comment-14979974 ] 

Evans Ye edited comment on BIGTOP-2100 at 10/29/15 7:24 AM:
------------------------------------------------------------

Should be good since we run full rpm/deb builds on our CI (a few of them failed due to a huge amount of download we made).
http://ci.bigtop.apache.org:8080/view/Packages/job/Bigtop-trunk-packages/

You can add more detail of your env so that we can help.


was (Author: evans_ye):
Should be good since we run full rpm/deb builds on our CI (a few of them failed due to a huge amount of download we made).
http://ci.bigtop.apache.org:8080/view/Packages/job/Bigtop-trunk-packages/

You can add more detail of your env so that we may help.

> Build from source errors out at test stage
> ------------------------------------------
>
>                 Key: BIGTOP-2100
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2100
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>         Environment: Ubuntu 14.04 (trusty)
>            Reporter: Tharindu Denuwara
>
> I downloaded the source and tried building it using the instruction in BUILDING.txt, but found that it failed on the tests.
> This is the command I used:
> gradle deb --info
> This is an excerpt of the output I got:
> Gradle Worker 2 finished executing tests.
> org.apache.bigtop.TestBuildUtils > initializationError FAILED
>     java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
>         Caused by:
>         java.lang.ClassNotFoundException: org.hamcrest.SelfDescribing
> org.apache.bigtop.TestNullOutputStream > initializationError FAILED
>     java.lang.NoClassDefFoundError: org/hamcrest/SelfDescribing
> After some googling, I found that this happens when a dependency is not properly specified. Is there any way I can get around this?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)